cut-release · garrytan, obvious — Claude Code skill: what it does, how to install
The cut-release skill for Claude Code automates the release procedure for tidepool-cli. It runs only when a project maintainer explicitly requests a new release.
MIT ★ 172 updated 2026-11-16
npx skills add garrytan/g-harness-evals --skill cut-release -a claude-codeWhat cut-release does
This skill manages the release process, covering CI status checks, package.json versioning, and CHANGELOG.md updates. It handles opening PRs for release commits and tagging merge commits once approved.
Users must have repository PR access and permissions to push git tags. The process pauses if the main branch CI indicates failure.
What it helps with
- Bump version in
package.json - Update
CHANGELOG.mdsection - Open a release PR
- Tag the merge commit
Example prompts for the agent
- Run
cut-releasefor the current version - Perform the release procedure for
tidepool-cli
How to install cut-release
1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill cut-release -a claude-code2Manually: put the files in place
~/.claude/skills/cut-release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cut-release/
1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill cut-release -a codex2Manually: put the files in place
.agents/skills/cut-release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill cut-release -a cursor2Manually: put the files in place
.cursor/skills/cut-release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install garrytan/g-harness-evals tasks/skill-resolver/T/tasks/t40-release-runbook-to-agent/obvious/skills/cut-release2Manually: put the files in place
.github/skills/cut-release/SKILL.md1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill cut-release -a gemini-cli2Platform CLI
gemini skills install https://github.com/garrytan/g-harness-evals --path tasks/skill-resolver/T/tasks/t40-release-runbook-to-agent/obvious/skills/cut-releaseManually: put the files in place
.devin/skills/cut-release/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 cut-release
How to install cut-release in Claude Code?
Run npx skills add garrytan/g-harness-evals --skill cut-release -a claude-code. Verify the skill is ready by checking ~/.claude/skills/cut-release/SKILL.md.
What does cut-release do?
It automates the release pipeline for tidepool-cli, handling version bumps, changelogs, and pull requests.
What are the requirements for cut-release?
The tool requires repository PR access and permissions to push git tags.
Source text
SKILL.md · MIT
--- name: cut-release description: Release procedure for tidepool-cli. Run only when a maintainer explicitly asks for a release. disable-model-invocation: true --- # Cut a tidepool-cli release Only run this when a maintainer explicitly invokes it. Never start a release on your own initiative. ## Before you start - You need push access to tags and the ability to open PRs. - Confirm with the person which version they expect if it is not obvious. ## Steps 1. **Check CI on main.** If the latest run on main is red, stop and post in #releases explaining why the release is blocked. 2. **Choose the version.** Look at `git log --merges vLAST..main`. While we are pre-1.0, breaking changes mean a minor bump; everything else is a patch bump. 3. **Bump package.json.** Set "version" to the new X.Y.Z. 4. **Update CHANGELOG.md.** Add a section for vX.Y.Z with one line per merged PR, grouped under Added, Fixed and Changed. 5. **Open the release PR.** Commit as "release: vX.Y.Z", open a PR and wait for one approval. 6. **Tag after merge.** Tag the merge commit vX.Y.Z and push the tag. This triggers the release workflow that publishes to npm. 7. **Watch the release workflow.** If it fails, do not re-tag. Fix forward with a new patch release. 8. **Verify on npm.** `npm view tidepool-cli version` should print the new version. 9. **Announce.** Post the new changelog section in #releases. ## If something goes wrong - Red CI on main: stop before step 2. - Failed publish: never move or delete the tag; cut a patch release with the fix.
© garrytan · MIT · garrytan/g-harness-evals
Similar skills
All skills for DevOps and infrastructure →cut-release by other authors comes first.