agentleFS
tejastn10tejastn10/workbench/skills/deployment/cut-release/SKILL.md

cut-release

Skill1 starsChanged 2 months agoMITView on GitHub

Cut a release the way Tejas's repos do it — derive the next semver from conventional-commit history, write grouped release notes, tag `vX.Y.Z`, and let the tag-triggered workflow build. Use when asked to "cut a release", "bump the version", "tag a release", "prepare release notes", or "what's the next version".

  • Commits and pushes

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 5 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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a CHANGELOG.md exists, prepend the same content under a ## [X.Y.Z] - DATE heading.

    line 51
  2. Distinctive:

    Commit and tag as the configured git user.

    line 64

“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 release

Their release pipeline is tag-triggered: pushing a v*.*.* tag runs release.yml / docker-image.yml (cross-compile or buildx multi-arch, GHCR + Docker Hub, softprops/action-gh-release). This skill covers everything up to and including the tag.

1. Determine the next version

Semver, decided from conventional commits since the last tag (git describe --tags --abbrev=0 → git log <last>..HEAD):

Commits since last tagBump
any feat!: / fix!: / BREAKING CHANGE:major
any feat: (no breaking)minor
only fix: / perf: / refactor: / chore:patch

Pre-1.0 (0.x): a breaking change bumps minor, a feature bumps patch — flag this and confirm with the user.

2. Write the release notes

Group commit subjects by type, most user-facing first. Match the house format seen in argus / halcyon release.yml:

# <Name> vX.Y.Z 🚀

## ✨ Features
- <feat subjects>

## 🐛 Fixes
- <fix subjects>

## 🔧 Maintenance
- <refactor / perf / chore / build / ci subjects>

## 📦 Docker Images       ← only if the repo publishes images
- `docker.io/tejastn10/<repo>:X.Y.Z`
- `ghcr.io/tejastn10/<repo>:X.Y.Z`
  • Drop pure docs: / test: / style: noise unless notable.
  • Rewrite terse subjects into readable lines; keep them one clause each.
  • If a CHANGELOG.md exists, prepend the same content under a ## [X.Y.Z] - DATE heading.

3. Tag and push

git checkout main && git pull
# update version in package.json / pyproject.toml / a constants file if the repo tracks it there
git commit -m "chore(release): vX.Y.Z"      # only if a version file changed
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin main --follow-tags

Commit and tag as the configured git user. Never co-author. Don't push unless the user asked.

4. Verify

  • The Release / Build and Publish Docker Image workflow went green.
  • The GitHub Release exists and the notes render.
  • Published artifacts / images are pullable at the new tag.
  • latest only moved if the tag was on the default branch.

Anti-patterns

  • ❌ Guessing the bump instead of reading the commit history.
  • ❌ A version file bumped in one place but not the others.
  • ❌ Tagging off a feature branch.
  • ❌ Hand-running the Docker build the workflow already does.
  • ❌ Empty ## Changelog section when the commits could fill it.

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.