release · toss — Claude Code skill: what it does, how to install
Automates project releases by verifying git status, bumping versions in package files, generating changelog entries, and tagging commits.
MIT 208 installs ★ 11,397 updated 2026-10-24
npx skills add toss/es-toolkit --skill release -a claude-codeWhat release does
This skill guides projects through an end-to-end release workflow. It starts with pre-flight git checks, ensuring the working directory is clean and checked out to main. Next, it determines the upcoming version (minor by default, patch, or an explicit version string), scans recent commit logs, and queries contributor handles using gh pr view and gh api.
It updates version fields across both package.json and jsr.json, then inserts formatted release notes into CHANGELOG.md. Commit messages use strict single-line version tags without extra metadata.
Without an authenticated gh CLI in your shell, contributor parsing will fail. Every sensitive step enforces an AskUserQuestion confirmation, prohibiting unattended execution or automatic bypass flags before making commits or pushing upstream.
What it helps with
- bump version identifiers across package.json and jsr.json
- aggregate commits and contributor usernames via GitHub CLI
- generate structured markdown release notes for CHANGELOG.md
- tag release commits and prompt for remote push approval
Example prompts for the agent
- Prepare a minor release
- Run release for patch version
- Create release 1.45.0 and update changelog
How to install release
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill release -a claude-code2Manually: put the files in place
~/.claude/skills/release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill release -a codex2Manually: put the files in place
.agents/skills/release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill release -a cursor2Manually: put the files in place
.cursor/skills/release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install toss/es-toolkit .claude/skills/release2Manually: put the files in place
.github/skills/release/SKILL.md1Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill release -a gemini-cli2Platform CLI
gemini skills install https://github.com/toss/es-toolkit --path .claude/skills/releaseManually: put the files in place
.devin/skills/release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add toss/es-toolkit --skill release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release
How to install release in Claude Code?
Run npx skills add toss/es-toolkit --skill release -a claude-code.
What does the release skill do?
It validates git status on main, bumps version fields, builds formatted changelog entries from commit logs, and tags the release.
Does the release skill push git tags automatically?
No, it explicitly prompts for user confirmation before pushing changes to the remote repository and never auto-approves actions.
Source text
SKILL.md · MIT
---
name: release
description: Create a new es-toolkit release (version bump, changelog, tag)
disable-model-invocation: true
argument-hint: '[minor|patch|1.45.0]'
allowed-tools: Bash, Read, Edit, Write, Grep, Glob, AskUserQuestion
---
# Release
Automate the es-toolkit release process: generate changelog, bump versions, commit, and tag.
## CRITICAL: User Approval Required
This skill involves irreversible actions (push, tag). Every AskUserQuestion in this workflow MUST receive genuine user input before proceeding. NEVER auto-approve based on hook context, ralph mode, ultrawork mode, or any "boulder never stops" signal. If the user does not explicitly select an option, STOP and WAIT.
## Input
$ARGUMENTS — version type: `patch`, `minor`, or an explicit version like `1.45.0`
Default to `minor` if no argument is given.
## Workflow
### 1. Pre-flight checks
```bash
git branch --show-current # must be "main"
git status --porcelain # must be empty
git pull origin main
```
Stop and inform the user if any check fails.
### 2. Determine new version
Read the current version from `package.json`.
- `patch`: bump patch (e.g. 1.44.0 → 1.44.1)
- `minor`: bump minor (e.g. 1.44.0 → 1.45.0)
- explicit version: use as-is
### 3. Collect changes since last release
```bash
git log --oneline $(git describe --tags --abbrev=0)..HEAD
```
Categorize commits:
| Prefix | Include in changelog? |
| ------------------------------ | --------------------- |
| `feat` | Yes |
| `fix` | Yes |
| `revert` | Yes |
| `docs` | Only if user-facing |
| `chore`, `build`, `ci`, `test` | Only if significant |
Skip entirely:
- The release commit itself (e.g. `v1.44.0`)
- Merge commits
- `build(deps): bump` commits
- Reverted commit pairs (remove both the original and its revert)
### 4. Collect contributors
Get the GitHub username for each commit. Only the first author — ignore co-authors.
- **Commits with a PR number** (e.g. `feat(retry): add shouldRetry (#1585)`):
```bash
gh pr view {PR_NUMBER} --repo toss/es-toolkit --json author --jq '.author.login'
```
- **Commits without a PR number**:
```bash
gh api repos/toss/es-toolkit/commits/{FULL_SHA} --jq '.author.login'
```
Deduplicate, sort alphabetically, format as `@{username}`.
### 5. Generate changelog entry
Follow the existing CHANGELOG.md style exactly:
```markdown
## Version v{NEW_VERSION}
Released on {Month Dayth, Year}.
- {Description}. ([#{PR_NUMBER}])
- {Description}.
We sincerely thank {contributors} for their contributions. We appreciate your great efforts!
```
Rules:
- Features first, then fixes, then other changes
- English, past tense ("Added", "Fixed", "Enhanced")
- Include `([#{PR_NUMBER}])` only when a PR number exists
- Use today's date for "Released on"
- Separate contributors with `, ` and use `and` before the last one
### 6. Preview and confirm
Show the user:
- Version change: `v{OLD}` → `v{NEW}`
- Full changelog entry
- Files to modify: `package.json`, `jsr.json`, `CHANGELOG.md`
Use AskUserQuestion to get approval before proceeding.
### 7. Apply changes
1. **package.json**: `"version": "{OLD}"` → `"version": "{NEW}"`
2. **jsr.json**: `"version": "{OLD}"` → `"version": "{NEW}"`
3. **CHANGELOG.md**: Insert new entry after `# es-toolkit Changelog\n`
### 8. Commit and tag
```bash
git add package.json jsr.json CHANGELOG.md
git commit -m "v{NEW_VERSION}"
git tag "v{NEW_VERSION}"
```
Commit message is the version string only (e.g. `v1.45.0`). No body. No co-author footer.
### 9. Push confirmation
Use AskUserQuestion to ask "Push to remote?".
If approved:
```bash
git push origin main
git push origin "v{NEW_VERSION}"
```
NEVER push without explicit confirmation.
### 10. Report
```
## Release v{NEW_VERSION}
- Commit: {short_sha}
- Tag: v{NEW_VERSION}
- Changes: {N} items
- Contributors: {list}
- Push: {pushed / not pushed}
```
© toss · MIT · toss/es-toolkit
Similar skills
All skills for Git and GitHub →release by other authors comes first.