Results for “versioning”

Builds reusable CircleCI Orbs with the Orb SDK and orb-tools pipeline, packaging commands, executors, and jobs with automated semantic versioning.

Defines RESTful API design conventions including URL structure, status codes, error formats, pagination, versioning, rate limiting, CORS, validation, and OpenAPI documentation.

Migrate .NET projects from per-project package versioning to NuGet Central Package Management (CPM) using Directory.Packages.props, with baseline build capture, version conflict resolution, and post-conversion validation.

Automates semantic versioning and release workflow for Claude Code plugins, including version increments across multiple manifest files, build verification, git tagging, GitHub releases, and changelog generation.

Enforces the Vikingo Studio standard for WordPress plugins and repos: naming taxonomy, plugin headers, folder structure, versioning, release flow, private update channel, admin UI rules, security baseline, and pre-release checklist.

Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.

Manage notes, bookmarks, and notebooks using the nb CLI. Create, list, search, and organize notes across multiple notebooks with Git-backed versioning.

Flyway database migrations for Spring Boot applications. Covers migration scripts, versioning, callbacks, and rollback strategies. Based on production patterns from castellino and gestionale-presenze projects. USE WHEN: user mentions "flyway", "database versioning", "Java migrations", "Spring Boot migrations", "V1__", "migration checksum" DO NOT USE FOR: general migration strategies - use `migrations` instead, Liquibase - use specific tool skill, Prisma/TypeORM - use respective skills

Provides RESTful API design patterns and best practices for creating endpoints, designing APIs, and implementing routes.

Provides RESTful API design patterns and best practices for creating endpoints, designing APIs, and implementing routes.

Generate consistent, auditable release notes from Conventional Commits, compute semantic version bumps, and enforce commit format linting.

Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.

Define version control strategies for design files, component libraries, and design assets to enable team collaboration and consistency.

Write changelogs and release notes that users actually read, with guidance on categorization, user-facing language, visuals, and distribution.

Version bump, generate changelog, tag, and prepare a release

Use when the user asks to release, version, tag, or publish.

Develop reusable library code across languages. Use when designing public APIs, organizing modules, managing versioning, or creating utility libraries. Provides foundational patterns that language-specific *-lib-* skills extend.

Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across multiple parallel streams.

Begins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either an explicit version or a natural-language description of the release.

MVCC (Multi-Version Concurrency Control)

Migrates code between frameworks, versions, or patterns safely

URL-driven website cloning with visual + functional verification

Version control for ArcGIS web maps, exposed as native OpenClaw tools.

Guides open source license selection, comparison, compliance review, and drafting of LICENSE/NOTICE files using canonical texts.

Imported skill redlining from anthropic

Extract a bounded part of the invoking codebase into a new GitHub repository with private and public-OSS readiness gates

通用多轮迭代改进：对任意研究制品反复调用 /review → 解析反馈 → 修复 → 更新 wiki，直到达标

当完成一个创作（文章、产品原型等）后，因自我怀疑或追求完美而犹豫是否发布时

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Sets up Git-based version control for data science projects, handling notebooks, datasets, and pipelines with DVC and nbstripout.