// Release a new version of the itsvertical npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
Manage projects with the Vertical board using the itsvertical CLI. Create projects, add tasks, organize boxes, split layers, and track progress. Use when the user mentions Vertical, project management, boxes, slices, .vertical files, or itsvertical.
Create, manage, and debug Claude Code Agent Skills. Use when creating new skills, debugging skill activation issues, writing SKILL.md files, managing skill structure, or learning about Claude Code skills. Helps with personal skills, project skills, YAML frontmatter, descriptions, and troubleshooting.
Write and run unit tests with Vitest. Use when writing tests, adding test coverage, debugging test failures, or when the user mentions testing, vitest, unit tests, or test-driven development.
| name | release |
| description | Release a new version of the itsvertical npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version. |
| metadata | {"internal":true} |
Automate the release workflow for the itsvertical npm package.
Find the latest git tag:
git tag --list 'v*' --sort=-version:refname | head -1
Read the current version from package.json.
Get the diff since the last release tag:
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat
Determine the next version following semver. Since we're on 0.0.x, breaking changes can go in patch releases. Bump the patch version unless the user specifies otherwise.
Edit package.json to set the new version number.
pnpm install
This updates the lockfile with the new version.
pnpm run lint-fix && pnpm run tsc && pnpm run test && pnpm run build
All must pass before proceeding.
Commit package.json and pnpm-lock.yaml with message v<new-version>. Push to main.
Tell the user to run:
npm publish
Do not run npm publish yourself — it requires an OTP. Wait for the user to confirm they've published before continuing.
Once the user confirms the publish, create a GitHub release.
Write release notes by analyzing the diff between the previous tag and HEAD. Follow the pattern from previous releases:
### What's new section with bullet points for each notable change### Also in this release section for minor changes (if any)### New contributors section if there are first-time contributors (see below)**Full diff** link at the endFind all contributors in this release and compare against previous releases:
# Contributors in this release
gh pr list --state merged --search "merged:>=<last-tag-date>" --json author --jq '.[].author.login' | sort -u
# All previous contributors
git log <last-tag> --format="%aN" | sort -u
For each new contributor, add a line like:
- @username made their first contribution in #<PR-number> 🎉
Use this format for the full diff link:
**Full diff**: https://github.com/seasonedcc/vertical/compare/v<previous>...v<new>
Create the release:
gh release create v<new-version> --title "v<new-version>" --notes "<release-notes>"
Use a HEREDOC for the notes to preserve formatting.