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
- GLinnik21/plx-nativetheir own version, first seen Nov 8, 2026
- mediajunkie/piper-morgan-producttheir own version, first seen Nov 8, 2026
- delexw/motion-graphics-agenttheir own version, first seen Nov 8, 2026
- V-Songbird/foundrytheir own version, first seen Nov 4, 2026
- tansu-io/tansutheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
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.
layer5ioSkillquota-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
SentrySkilliterate-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
layer5ioSkillgh-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
kunchenguidSkillchrome-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
kunchenguidSkilllavish
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
ThisIsSadeghiSkillverify-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
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- ToolJet/ToolJet★ 41ksame name
- meshery/meshery★ 12ksame name
- danielmeppiel/apm★ 4.2ksame name
- microsoft/apm★ 4.2ksame name
- Screenly/Anthias★ 3.7ksame name
- Netflix/bpftop★ 2.7ksame name
- tansu-io/tansu★ 1.9ksame name
- fim-ai/fim-agent★ 1.6ksame name
- fim-ai/fim-one★ 1.6ksame name
- libredb/libredb-studio★ 1.3ksame name
26 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bigquery-analyticsSkill
- cache-invalidationSkill
- mongo-aggregationSkill
- mongo-modelingSkill
- postgres-aggregationSkill
- postgres-indexingSkill
- redis-coordinationSkill
- redis-patternsSkill
- review-querySkill
- code-migrationSkill
- data-migrationSkill
- deploy-serviceSkill
- hotfixSkill
- rollbackSkill
- design-endpointSkill
- design-eventSkill
- design-schemaSkill
- evolve-contractSkill
- scaffold-nestjs-moduleSkill
- scaffold-projectSkill
- incident-responseSkill
- investigate-bugSkill
- on-callSkill
- postmortemSkill
- audit-skillsSkill
- distill-review-styleSkill
- write-skillSkill
- debug-with-tracesSkill
- define-alertsSkill
- instrument-serviceSkill
- evaluate-dependencySkill
- grillSkill
- handoffSkill
- orientSkill
- phased-deliverySkill
- spikeSkill
- to-questionnaireSkill
- write-adrSkill
- write-prdSkill
- devops-pr-reviewSkill
- go-backend-pr-reviewSkill
- nestjs-backend-pr-reviewSkill
- python-backend-pr-reviewSkill
- react-frontend-pr-reviewSkill
- bisectSkill
- break-couplingSkill
- dead-code-sweepSkill
- deslopifySkill
- extract-moduleSkill
- rebase-cleanSkill
- resolve-merge-conflictsSkill
- split-commitSkill
- tddSkill
- wait-whatSkill
- wide-renameSkill
- bullmqSkill
- kafkaSkill
- sqs-consumerSkill
- audit-dependenciesSkill
- The first 60 shown.
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
- Very specific: line 51
If a CHANGELOG.md exists, prepend the same content under a ## [X.Y.Z] - DATE heading.
- Distinctive: line 64
Commit and tag as the configured git user.
“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.
Files
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 tag | Bump |
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.mdexists, prepend the same content under a## [X.Y.Z] - DATEheading.
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-tagsCommit 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 Imageworkflow went green. - The GitHub Release exists and the notes render.
- Published artifacts / images are pullable at the new tag.
latestonly 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
## Changelogsection when the commits could fill it.
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
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.

