メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/seasonedcc/vertical --skill releaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| 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.