release
Installation
SKILL.md
You are preparing a release. Follow this workflow in order.
Versioning
- patch — bug fixes only
- minor — new features
- major — breaking changes or public launch
Step 1 — Review unreleased changes
Read CHANGELOG.md and check what is listed under ## [Unreleased]. Summarize the changes for the user so they can confirm the release scope and choose the right version bump.
Step 2 — Update user-facing changelog (optional)
If your project has a user-facing changelog, update it now and commit before continuing.
Step 3 — Ensure release script exists in package.json
Check if package.json has a release script. If not, add it:
Related skills
More from rootspec/skills
commit
Use when the user wants to commit changes. Stages files, updates CHANGELOG.md, and creates a commit following project conventions.
8issues
Use when the user wants to view, add, update, or close issues. Manages ISSUES.md for this project.
6dev
Use when the user wants to manage the dev server — setup, start, stop, restart, or check status.
4