菜单
Determines appropriate semantic version bumps based on changes. Use when deciding version numbers, evaluating breaking changes, or planning releases. Triggers on terms like "version", "semver", "breaking change", "major/minor/patch".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Automates the release process for this Rust project. Use when creating a new release, preparing a version bump, or publishing to GitHub/crates.io. Triggers on terms like "release", "publish", "version bump", "create tag".
Update the ADR inventory table in docs/adrs/README.md by scanning all adr-*.md files, extracting their title, status, and date. Use when a new ADR is added or an existing ADR's status or title has changed.
Reviews and updates `insta` golden snapshots after changes to user-visible CLI surface (subcommands, flags, help text, error messages). Invoke whenever a change touches `src/cli/**`, `src/main.rs`, `#[derive(Parser)]`, or `#[arg(...)]` sites — *before* declaring the work done. Triggers on terms like "snapshot", "insta", "golden", "help_all", and "snap".
Validates and corrects commit messages against project guidelines after a commit is created. Invoke automatically after every git commit to ensure messages conform to .omni-dev/commit-guidelines.md.
Formats markdown tables with fixed-width columns for consistent alignment. Use when creating tables, reformatting existing tables, or ensuring table readability. Triggers on terms like "format table", "align table", "fix table", "table columns".
Manages CHANGELOG.md entries following Keep a Changelog format. Use when adding changelog entries, documenting changes, updating release notes, or preparing for a release. Triggers on terms like "changelog", "document changes", "release notes", "what changed".
| name | version-bump |
| description | Determines appropriate semantic version bumps based on changes. Use when deciding version numbers, evaluating breaking changes, or planning releases. Triggers on terms like "version", "semver", "breaking change", "major/minor/patch". |
This skill helps determine appropriate version bumps following Semantic Versioning.
MAJOR.MINOR.PATCH
Bump MAJOR when you make incompatible API changes:
Bump MINOR when you add functionality in a backwards compatible manner:
Bump PATCH when you make backwards compatible bug fixes:
| Change Type | Version Bump |
|---|---|
| Breaking API change | MAJOR |
| Removed feature | MAJOR |
| New command/feature | MINOR |
| New CLI flag | MINOR |
| New provider/integration | MINOR |
| Bug fix | PATCH |
| Performance fix | PATCH |
| Documentation only | PATCH |
| Refactoring (no behavior change) | PATCH |
For versions < 1.0.0 (like this project):
Review all changes since last release:
git log --oneline $(git describe --tags --abbrev=0)..HEAD
Check for breaking changes:
If breaking changes exist -> MAJOR bump
If new features exist -> MINOR bump
If only fixes/refactoring -> PATCH bump
When bumping version, update:
version = "X.Y.Z"## [X.Y.Z] - YYYY-MM-DD section