prepare-release
Skill2 starsChanged 10 days agoMITView on GitHub
Prepare an AntanI release PR. Bumps the version in tauri.conf.json, Cargo.toml, and package.json in sync, branches from main, commits, pushes, and opens a PR titled "Release vX.Y.Z" via gh. Use when the user asks to prepare/cut/ship a release, or says something like "prepare the release PR" or "release vX.Y.Z".
- Commits and pushes
49 other projects use a version of this.
Adopted by
Most recently taken up by
- Krzysztof318/MailFathomtheir own version, first seen Nov 15, 2026
- erraggy/oastoolstheir own version, first seen Nov 15, 2026
- CherryHQ/cherry-studiotheir own version, first seen Nov 15, 2026
- leancodepl/patroltheir own version, first seen Nov 9, 2026
- Azure/azure-sdk-for-rusttheir own version, first seen Nov 8, 2026
- epam/ketchertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use publish-release, sync-docs and 7 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.
Model Context ProtocolSkillpublish-release
Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a release, create release notes, or complete a release after the prepare-release PR has been merged.
Also in 4 projects that use this
MichaelRyanWoodSkillsync-docs
Audit and update AI support documentation (ARCHITECTURE.md, SECURITY.md, CLAUDE.md, diagrams/) to reflect recent code changes. Run after completing a feature, fix, or refactor to keep docs accurate.
Also in 4 projects that use this
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 3 projects that use this
DockerSkillfix-issue
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".
Also in 4 projects that use this
kiminmonacoSkillimplement-feature
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
Also in 3 projects that use this
SentrySkillwrite-docs
Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.
Also in 3 projects that use this
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- CherryHQ/cherry-studio★ 54ksame name
- redis/go-redis★ 22ksame name
- netbox-community/netbox★ 22ksame name
- joke2k/faker★ 19ksame name
- pybind/pybind11★ 18ksame name
- telepresenceio/telepresence★ 7.3ksame name
- modelcontextprotocol/csharp-sdk★ 4.6ksame name
- CLIUtils/CLI11★ 4.5ksame name
- tmoroney/auto-subs★ 4.5ksame name
- ethereum/consensus-specs★ 4ksame name
39 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- adding-tauri-commandSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
2
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 21
Current version: read .version from src-tauri/tauri.conf.json — this is the single source of truth for "current version."
- Distinctive: line 24
Target version: if the user gave an explicit version (e.g.
- Distinctive: line 56
Write a 1–2 sentence plain-English summary of what the change actually does from a user's perspective — not a restatement of the commit …
“Common” is measured: kept by at least 6 in 10 of the 48 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
Prepare an AntanI release
Merging a PR titled Release vX.Y.Z into main is what triggers
.github/workflows/release.yml (build + draft GitHub Release), which in turn
triggers .github/workflows/bump-tap.yml on publish (updates the
skixmix/homebrew-antani tap). This skill only prepares and opens that PR —
it never merges, publishes a release, or touches the tap directly.
Steps
- Preconditions:
gh auth statusmust succeed (if not, tell the user to rungh auth loginthemselves — never attempt to log them in). Working tree must be clean; if not, stop and ask rather than stashing/discarding. Checkout and pullmain. - Current version: read
.versionfromsrc-tauri/tauri.conf.json— this is the single source of truth for "current version." - Target version: if the user gave an explicit version (e.g. "release
v0.2.0"), use it. Otherwise inspect commits since the last
vX.Y.Ztag (git log <last-tag>..main --oneline) and suggest a bump using conventional-commit-ish signal: a!after the type or aBREAKING CHANGEfooter -> major; anyfeat:-> minor; otherwise -> patch. Always confirm the suggested version with the user via AskUserQuestion before proceeding — never assume. Bump in sync, exact same version string in all three:
src-tauri/tauri.conf.json("version"field)src-tauri/Cargo.toml(version = "..."under[package]; BSD sed has no0,/re/address, so edit that line explicitly)package.json("version"field)
Then refresh
src-tauri/Cargo.lockso itsantanientry matches (cargo update -p antani --offlineinsrc-tauri). A lagging lockfile breaks any--lockedbuild.- Branch:
git checkout -b release/vX.Y.Zfrommain. - Commit:
git commit -am "Release vX.Y.Z"— only the three version files plusCargo.lock, nothing else. If other unrelated changes are staged/dirty, stop and ask first. - Push:
git push -u origin release/vX.Y.Z. Build release recap from
git log <last-tag>..main --oneline(same range used for version signal in step 3). For each commit:- Fetch its diff (
git show <sha> --stat) and, if a PR number is present, fetch the PR body viagh pr view <number> --json body,titlefor extra context. - Write a 1–2 sentence plain-English summary of what the change actually does from a user's perspective — not a restatement of the commit title. Focus on the observable effect, not the implementation.
- Categorize case-insensitively by conventional-commit prefix:
feat:/feat!:→ Features,fix:→ Bug fixes, everything else → Improvements. Omit the version-bump commit itself. - Omit a section entirely if it has no entries.
Example output:
## Features - Tabs can now be dragged between split panes — drop a tab onto any pane header to move it there instantly. (#37) ## Bug fixes - The sidebar now correctly highlights the active project even when collapsed to icon-only mode. - Projects reorder correctly after a drag; the previous ordering glitch on drop is fixed. ## Improvements - The split-pane preview is now shown while dragging, giving clearer visual feedback before you drop.- Fetch its diff (
- Open the PR — title must start with exactly
Release(this is whatrelease.ymlmatches on the squash-merge commit message). Use the recap from step 8 as the top of the body, followed by the release instructions:gh pr create --title "Release vX.Y.Z" --base main --head release/vX.Y.Z \ --body "$(cat <<'EOF' <recap sections here> --- Version bump only. Merging triggers the build + draft release; publish it manually to update the Homebrew tap. EOF )" - Report the PR URL back to the user, and remind them of the two manual gates still ahead: merging this PR (once CI + review pass) and clicking Publish on the resulting draft GitHub Release.
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.

