cut-release · garrytan, oracle — Claude Code skill: release tidepool-cli
cut-release is a Claude Code skill that releases tidepool-cli when explicitly invoked with /cut-release. It checks CI, prepares a PR, publishes a tag, and posts in #releases.
MIT ★ 172 updated 2026-11-16
npx skills add garrytan/g-harness-evals --skill cut-release -a claude-codeWhat cut-release does
cut-release follows docs/release-runbook.md to release tidepool-cli. It checks the latest CI run on main, then chooses a version from merged PRs: a breaking change before 1.0 calls for a minor bump; otherwise, it picks a patch. The skill updates package.json and adds a CHANGELOG.md section with one line per merged PR, grouped under Added, Fixed, and Changed.
It creates a release: vX.Y.Z commit and opens a PR. After approval and merge, it tags the merge commit and monitors the publishing workflow. A failed workflow means no second tag; the recovery path is a patch release. The final checks use npm view tidepool-cli version and post the changelog section to #releases.
What it helps with
- choose a version based on merged PRs and breaking changes
- update
package.jsonand group merged PR notes inCHANGELOG.md - open a release PR, tag its merge commit, and monitor publishing
- verify the published version and announce it in
#releases
Example prompts for the agent
- Run
/cut-releaseto release a new tidepool-cli version. - Use
/cut-releaseto prepare and publish the next tidepool-cli release. - Run the release process from
docs/release-runbook.mdwith/cut-release.
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/oracle/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/oracle/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 do I install cut-release in Claude Code?
Run npx skills add garrytan/g-harness-evals --skill cut-release -a claude-code. The skill file is at ~/.claude/skills/cut-release/SKILL.md.
What does cut-release do?
It manages a tidepool-cli release: selects a version, updates package.json and CHANGELOG.md, opens a PR, publishes a tag, then posts the result in #releases.
What does cut-release need to run?
Its workflow uses git to list merged PRs and npm to check the published tidepool-cli version.
Source text
SKILL.md · MIT
--- name: cut-release description: Cut a tidepool-cli release on request. Picks the version, updates package.json and CHANGELOG.md, tags, watches the publish and announces in #releases. disable-model-invocation: true --- # Cut a tidepool-cli release Run only when someone invokes /cut-release. Source: docs/release-runbook.md. ## Workflow 1. Check main is green. - Read the latest CI run on main. - If it is red, stop and tell #releases. - **Done when:** the latest main CI run is green, or the release is stopped and #releases is told why. 2. Pick the version. - List merged PRs since the last tag: `git log --merges vLAST..main`. - Breaking change while pre-1.0: minor bump. Otherwise: patch bump. - **Done when:** the new version vX.Y.Z is chosen and the reason (breaking or not) is stated. 3. Update package.json and CHANGELOG.md. - Set "version" in package.json to X.Y.Z. - Add a CHANGELOG.md section for vX.Y.Z, one line per merged PR, grouped under Added, Fixed and Changed. - **Done when:** package.json shows X.Y.Z and CHANGELOG.md has a vX.Y.Z section covering every merged PR from step 2. 4. Open the release PR. - Commit as "release: vX.Y.Z" and open a PR. - **Done when:** the PR is approved once and merged. 5. Tag and publish. - Tag the merge commit vX.Y.Z and push the tag; the tag push starts the release workflow. - Watch the workflow until it finishes. If it fails, do not re-tag; fix forward with a patch release. - **Done when:** the release workflow for vX.Y.Z has finished green. 6. Verify and announce. - Run `npm view tidepool-cli version`. - Post the vX.Y.Z changelog section in #releases. - **Done when:** npm reports X.Y.Z and the changelog section is posted in #releases.
© garrytan · MIT · garrytan/g-harness-evals
Similar skills
All skills for Data and databases →cut-release by other authors comes first.