Agent skill

Cut Release

by delexw in delexw/claude-code-trace

Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.

MITAuto-check passedDevelopment

Install Cut Release

skills CLI
$ npx skills add delexw/claude-code-trace --skill cut-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install delexw/claude-code-trace cut-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/delexw/claude-code-trace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cut-release .claude/skills/cut-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cut-release
GitHub stars
377
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
598 words
Files
13 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.

  • Works in 9 steps: Inspect and decide → Build the release branch → Bump version files → …
  • The GitHub Actions release pipeline
  • SKILL.md covers Operating mode, Before you start, Execution and What the skill will NOT do…
  • Calls git, gh and npm

What it does

Cut Release is an agent skill from delexw/claude-code-trace. Cuts a new versioned release of claude-code-trace end-to-end without asking any questions. Detects commits since the last ancestral tag, classifies them with conventional-commit rules to pick the semver bump, bumps every version-bearing file in sync, writes the CHANGELOG entry, commits and tags on a release branch, pushes the tag to trigger the GitHub Actions release pipeline, fast-forwards main onto the release commit and pushes it, then cleans up the local branch. Use this skill whenever the user mentions…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files (for example `references/changelog-template.md`, `references/conventional-commits.md` and `references/project-shape.md`).

It sits in Development, covering Commit messages, Changelog and release notes and CI/CD. It works with GitHub Actions, React, Tauri and Rust. The repository describes itself as: Claude Code session log viewer for JSONL files in ~/.claude/projects. Browse conversations, tool calls, tokens, and live tail sessions on desktop, web, and TUI. The licence is MIT.

When your agent uses it

  • The GitHub Actions release pipeline
  • Fast-forwards main onto the release commit and pushes it
  • Then cleans up the local branch
  • The user mentions cutting

Example prompts

  • “cut a release”
  • “release v1.2.3”
  • “tag and release”
  • “/cut-release”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Inspect and decide
  2. Build the release branch
  3. Bump version files
  4. Write the CHANGELOG entry
  5. Verify, commit, tag
  6. Push the tag (with duplicate-version preflight)
  7. Watch the pipeline and verify the release is public
  8. Push the release commit to main
  9. Clean up

What it can do on your machine

Read from SKILL.md and the folder at commit 833971e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cut Release loads about 1.4k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 222 tokens; SKILL.md has 598 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~222
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from delexw/claude-code-trace at commit 833971e, republished under its MIT licence (© delexw). 598 words, ~1,414 tokens.

Download SKILL.mdSave it as .claude/skills/cut-release/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
cut-release
description
Cuts a new versioned release of claude-code-trace end-to-end without asking any questions. Detects commits since the last ancestral tag, classifies them with conventional-commit rules to pick the semver bump, bumps every version-bearing file in sync, writes the CHANGELOG entry, commits and tags on a release branch, pushes the tag to trigger the GitHub Actions release pipeline, fast-forwards `main` onto the release commit and pushes it, then cleans up the local branch. Use this skill whenever the user mentions cutting, tagging, bumping, or shipping a release — including "cut a release", "release v1.2.3", "tag and release", "bump version", "publish a release", "do a patch release", or "make a new release". Trigger even when the user does not name the version — the skill computes it. Also use proactively when the user finishes a unit of work and asks to publish it.

Cut a Release — claude-code-trace

Turns "we should release this" into a tagged, pushed, pipeline-triggered, publicly published release with a curated CHANGELOG, in a way that survives the project's strict pre-commit hook chain and stays honest about what's actually shipping.

The skill is project-local because the steps depend on this repo's specific shape (three version files, two lockfiles, GH Actions release on v* tag, the spec-drift + test-reflection pre-commit hook pair).

Operating mode

The skill is fully automated end-to-end and fully synchronous. It never calls AskUserQuestion, never waits for "yes", never branches on user preference, and never runs any command in the background. Every Bash invocation runs in the foreground so the session holds continuously from Phase 1 through Phase 9 — no run_in_background: true, no trailing &, no nohup, no disown. This includes long-running steps like gh run watch in Phase 7; set the Bash timeout parameter to match the expected duration (e.g. 1800000 ms for the release pipeline) rather than detaching.

Defaults are deterministic:

  • Scope — always linear: every commit since git describe --tags --abbrev=0 ships.
  • Bump tier — highest conventional-commit tier in the subset (see ${CLAUDE_SKILL_DIR}/references/conventional-commits.md). BREAKING CHANGE: or !: produces a minor bump while the version is 0.X.Y (pre-1.0 caveat) and a major bump otherwise; the skill never silently promotes to 1.0.0.
  • CHANGELOG — every Added/Fixed bullet is written from commit subjects + diff reads; chore: / docs: / test: / ci: are always skipped.
  • Push order — tag first, then main (so CI sees the tag immediately; main catches up after).

The skill aborts (loudly) only on hard preconditions that would corrupt the release:

  • Duplicate version — the proposed vX.Y.Z tag already exists on origin. Abort with Error: vX.Y.Z already exists on origin (commit <sha>). Refusing to release the same version twice. The user must delete the remote tag intentionally if they want a re-release, or bump again.
  • Dirty working tree — uncommitted changes the skill didn't create. Abort with a list of dirty files.
  • npm run check fails — abort and surface the failure verbatim.

Before you start

Read these references on the first invocation in a session — they describe constants the phase files refer to.

  • ${CLAUDE_SKILL_DIR}/references/project-shape.md — version files, lockfiles, pre-commit hooks, release pipeline wiring.
  • ${CLAUDE_SKILL_DIR}/references/conventional-commits.md — how commit prefixes map to semver bump level.

${CLAUDE_SKILL_DIR}/references/changelog-template.md is loaded when you reach Phase 4.

Show full SKILL.md (226 more words)Show less

Execution

Phase 1 — Inspect and decide

Read ${CLAUDE_SKILL_DIR}/steps/phase1-inspect-and-scope.md and follow all instructions.

Phase 2 — Build the release branch

Read ${CLAUDE_SKILL_DIR}/steps/phase2-build-release-branch.md and follow all instructions.

Phase 3 — Bump version files

Read ${CLAUDE_SKILL_DIR}/steps/phase3-bump-versions.md and follow all instructions.

Phase 4 — Write the CHANGELOG entry

Read ${CLAUDE_SKILL_DIR}/steps/phase4-changelog.md and follow all instructions.

Phase 5 — Verify, commit, tag

Read ${CLAUDE_SKILL_DIR}/steps/phase5-verify-commit-tag.md and follow all instructions.

Phase 6 — Push the tag (with duplicate-version preflight)

Read ${CLAUDE_SKILL_DIR}/steps/phase6-push-tag.md and follow all instructions.

Phase 7 — Watch the pipeline and verify the release is public

Read ${CLAUDE_SKILL_DIR}/steps/phase7-publish-github-release.md and follow all instructions.

Phase 8 — Push the release commit to main

Read ${CLAUDE_SKILL_DIR}/steps/phase8-back-to-main.md and follow all instructions.

Phase 9 — Clean up

Read ${CLAUDE_SKILL_DIR}/steps/phase9-cleanup.md and follow all instructions.

What the skill will NOT do automatically

  • Bypass pre-commit hooks with --no-verify — always fix the underlying issue.
  • Force-push (git push -f) to main, the release tag, or any shared branch.
  • Delete a remote tag or remote branch.
  • Cut a major bump (X.0.0) while the version is still 0.X.Y — pre-1.0 the skill caps at minor even when a breaking change is detected.
  • Re-tag an existing version — the duplicate-version preflight in Phase 6 aborts first.

The harness's auto-mode classifier may still intercept pushes to shared branches (e.g. git push origin main) — that is out of skill scope. When it does, surface the error and continue with the remaining phases; the user resolves the push themselves.

© delexw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (references) in .claude/skills/cut-release of delexw/claude-code-trace.

  • SKILL.md
  • references/changelog-template.md
  • references/conventional-commits.md
  • references/project-shape.md
  • steps/phase1-inspect-and-scope.md
  • steps/phase2-build-release-branch.md
  • steps/phase3-bump-versions.md
  • steps/phase4-changelog.md
  • steps/phase5-verify-commit-tag.md
  • steps/phase6-push-tag.md
  • steps/phase7-publish-github-release.md
  • steps/phase8-back-to-main.md
  • steps/phase9-cleanup.md

Open the folder on GitHubat commit 833971e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in delexw/claude-code-trace, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Cut Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cut Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cut Release this skilldelexw/claude-code-trace3771 repos~1.4kAutomated safety check: PassMIT
Agentbro Releaseshirenchuang/agentbro203—~2.5kAutomated safety check: PassApache-2.0
Cline Desktop App Releasecline/cline70k—~4.5kAutomated safety check: PassApache-2.0
Release VersionGOODBOY008/r-shell153—~4kAutomated safety check: PassMIT
Code Reviewoaslananka/kicad-mcp-pro120—~3.9kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9.1k—~6.9kAutomated safety check: PassCustom licence

Similar skills

  • Agentbro Release

    shirenchuang/agentbro

    A skill your agent uses when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask…

    203 GitHub stars~2.5k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.

    70k GitHub stars~4.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Release Version

    GOODBOY008/r-shell

    Release a new r-shell version and create a published GitHub release with contributor credits.

    153 GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9.1k GitHub stars~6.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ccb GitHub

    SeemSeam/claude_codex_bridge

    Maintain this CCB project's GitHub-facing release and npm publication surface.

    3.6k GitHub stars~4.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

Categories

Questions about Cut Release

What does Cut Release do?

Cuts a new versioned release of claude-code-trace end-to-end without asking any questions. Cut Release is an agent skill from delexw/claude-code-trace. Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.

When should I use Cut Release?

Cut Release fits situations like: the GitHub Actions release pipeline; fast-forwards main onto the release commit and pushes it; then cleans up the local branch; the user mentions cutting.

How do I install Cut Release in Claude Code?

Run `npx skills add delexw/claude-code-trace --skill cut-release -a claude-code`. Or copy the skill folder (.claude/skills/cut-release in delexw/claude-code-trace) into .claude/skills/cut-release in your project. Claude Code loads it when a task matches its description.

How do I install Cut Release in Codex?

Run `npx skills add delexw/claude-code-trace --skill cut-release -a codex`. Or copy the skill folder (.claude/skills/cut-release in delexw/claude-code-trace) into .agents/skills/cut-release in your project. Codex loads it when a task matches its description.

Can I use Cut Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add delexw/claude-code-trace --skill cut-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cut-release, .gemini/skills/cut-release, .github/skills/cut-release and .opencode/skills/cut-release in your project.

What does Cut Release need to run?

Going by SKILL.md and its folder, Cut Release needs the command-line tools its instructions call (git, gh and npm).

Does Cut Release access the network?

SKILL.md contains no URLs. Its commands use git, gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cut Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cut Release use?

Cut Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cut Release use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Cut Release?

Skills that share tags, products or a category with Cut Release: Agentbro Release (shirenchuang/agentbro, 203 stars), Cline Desktop App Release (cline/cline, 70k stars), Release Version (GOODBOY008/r-shell, 153 stars) and Code Review (oaslananka/kicad-mcp-pro, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cut Release?

delexw (a GitHub user) maintains it in delexw/claude-code-trace, which has 377 GitHub stars. The repository was last updated on October 8, 2026.

Source: delexw/claude-code-trace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.