agentleFS
tenstorrenttenstorrent/tt-studio/.claude/skills/cut-release/SKILL.md

cut-release

Skill52 starsChanged 31 days agoApache-2.0View on GitHub

Orchestrate a TT-Studio release end-to-end with the maintainer release flags — cut an rc-vX.Y.Z branch from main (`python run.py --make-rc-branch`), cherry-pick dev hotfixes into it (`--update-rc-branch`), and ship it (`--merge-rc-branch` merges to main, pushes the vX.Y.Z tag that publishes the GHCR images, and creates the GitHub release) — delegating note-writing to the draft-release-notes skill. Use when someone asks to "cut a release", "make an RC", "update the RC", "ship vX.Y.Z", or "merge the RC branch".

  • Reads credentials

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quota-axi, iterate-pr and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • layer5ioSkill

    quota-axi

    Report local Claude, Codex, Cursor, GitHub Copilot, and Grok quota windows via the quota-axi CLI - remaining percentages, reset times, and provider status read from local auth sources, with no routing, recommendation, or provider mutation. Use before deciding whether it is safe to keep spending a provider's quota, when the user asks about usage, rate limits, or remaining quota, or when comparing local provider headroom.

    Also in 4 projects that use this

  • SentrySkill

    iterate-pr

    Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

    Also in 4 projects that use this

  • layer5ioSkill

    gh-axi

    Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, checking CI runs, triggering workflows, cutting releases, managing Projects boards, or managing Actions secrets/variables.

    Also in 4 projects that use this

  • kunchenguidSkill

    chrome-devtools-axi

    Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.

    Also in 4 projects that use this

  • kunchenguidSkill

    lavish

    Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.

    Also in 4 projects that use this

  • ThisIsSadeghiSkill

    verify-ui

    Verify UI implementation against Stitch design via a token audit (HTML ↔ Code, with X-component default-render checks) and an X-components compliance check.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    no RC branch yet → Cut

    line 26
  2. Distinctive:

    If main's tip moved between merge and tag (something else landed), the flag refuses to tag and prints the manual git tag command for the …

    line 99

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cut a TT-Studio release

The release model (CONTRIBUTING → Release Process): an rc-vX.Y.Z branch is cut from main, validated changes are cherry-picked from dev, the Rc vX.Y.Z PR is squash-merged back into main after ≥2 approvals, and the merge commit is tagged vX.Y.Z — the tag push is what builds and publishes the GHCR images. Git tags are the only version source of truth.

The three python run.py flags automate the mechanical parts. All of them are interactive, verify state before acting, and stop with a fix-it panel when something is off — prefer them over hand-rolled git/gh sequences.

0. Preflight

  • These flags need the GitHub CLI: gh auth status must pass with push access.
  • The flags never switch your checkout (the RC is created with plumbing and cherry-picked in a scratch worktree), so run them from any branch — including a dirty one. Stay on a branch that has the flags; main doesn't until this tooling ships.
  • Figure out which stage the user is at and jump to it:
    • no RC branch yet → Cut
    • RC exists, fixes landed on dev → Stabilize
    • RC approved and green → Ship

1. Cut

python run.py --make-rc-branch          # asks: bump major / minor / patch
python run.py --make-rc-branch minor    # or say it up front (also accepts vX.Y.Z)

Detects the latest release across tags, rc-v* branches, and Rc vX.Y.Z (#N) merge commits on main (they have drifted historically), cuts rc-vX.Y.Z from origin/main, pushes it, and opens the Rc vX.Y.Z PR against main with the release test-plan checklist. Relay the PR URL to the user. One release at a time: while an untagged rc-v* branch exists on origin, the cut refuses and points at --update-rc-branch / --merge-rc-branch (or closing the stray RC).

2. Notes

Draft the release notes with the draft-release-notes skill (it owns the house style — do not restate its rules here). After the user approves the draft, put it at the top of the RC PR description, keeping the test-plan checklist below:

gh pr edit rc-vX.Y.Z --body-file <notes+testplan.md>

3. Stabilize

As hotfixes land on dev during RC testing:

python run.py --update-rc-branch

Lists dev commits newer than the main commit the RC was cut from (releases are squashed into main, so that date is the cutoff — older dev commits need a manual git cherry-pick), minus ones already picked onto the RC, lets the user pick, cherry-picks oldest-first, and pushes. A conflict rolls back the failing pick and prints manual-resolution steps. Re-run draft-release-notes if the changeset moved meaningfully.

4. Ship

Once the PR has ≥2 approvals and green checks:

python run.py --merge-rc-branch

It verifies approvals/checks via gh, asks one explicit confirmation, then: squash-merges as Rc vX.Y.Z, tags the merge commit vX.Y.Z, pushes the tag (→ Publish images workflow → ghcr.io/tenstorrent/tt-studio/*), and creates the GitHub release seeded with GitHub's generated notes (categorized via .github/release.yml). Afterwards, upgrade the release body to the curated notes:

gh release edit vX.Y.Z --notes-file <curated-notes.md>

Watch the Publish images run: https://github.com/tenstorrent/tt-studio/actions/workflows/publish-images.yml

Gotchas

  • Duplicate image build: the tag push and the release-published event each trigger Publish images; the runs are serialized and idempotent. Expected — don't cancel or "fix" it.
  • Tags must be pushed from a maintainer machine (the flag does this). A tag pushed by a workflow with the default GITHUB_TOKEN would NOT trigger publishing.
  • rc-* branches keep IS_QB2 off in .env.default; only the QB2 launch branch ships it on. --make-rc-branch warns if it's set.
  • If main's tip moved between merge and tag (something else landed), the flag refuses to tag and prints the manual git tag command for the actual merge commit — follow that rather than re-running.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.