semver-helper
avegancafe 제작
Coding Agents & IDEs요약
Semantic Versioning 2.0.0 reference guide.
설명
이 스킬이 하는 일
Reference guide for Semantic Versioning 2.0.0 decisions. Covers when to increment MAJOR, MINOR, or PATCH, with a decision tree, real examples, pre-release naming, and common edge cases.
Cuts through the full semver spec with a decision tree and concrete examples, so you get an answer in seconds instead of reading documentation.
사용 시점
- Deciding whether removing a deprecated API endpoint requires a MAJOR bump
- Checking which number to increment before publishing an npm package
- Resolving the correct bump when a PR contains both a bug fix and a new feature
- Picking the right pre-release label (alpha, beta, rc) before a stable release
- Confirming whether an internal refactor that preserves behavior needs a version change
예시 워크플로
User asks: I renamed a public function from removeUser() to deleteUser() — what version should I bump to?
- 1
Check whether the change affects something users depend on
- 2
Identify the rename as a breaking change, since users must update all call sites
- 3
Apply the MAJOR bump rule: breaking changes increment the first number
- 4
Note that MINOR and PATCH reset to 0 after a MAJOR bump
Bump to the next MAJOR version (e.g. 1.2.3 → 2.0.0), since renaming a public function is a breaking API change.
설치
clawhub install avegancafe/semver-helperCLI 명령을 실행하거나, 프롬프트를 Claude Code, Cursor, Codex 등 사용하는 코딩 에이전트에 붙여넣으세요.