release
Skill0 starsChanged 13 days agoMITView on GitHub
Publish a new PR Radar version (bump on dev, PR dev → main, follow the release workflow). Use when the user asks for a release, a tag, or "ship vX.Y.Z".
- Installs packages
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 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.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Commit chore: release vX.Y.Z on dev (version bump and CHANGELOG.md together), with the Co-Authored-By trailer.
- Very specific: line 26
No manual tag: tauri-action creates the vX.Y.Z tag and the release.
- Very specific: line 27
Follow: gh run watch $(gh run list --workflow release.yml --limit 1 --json databaseId -q '.[0].databaseId').
- Very specific: line 28
Check the release: gh release view vX.Y.Z → assets present, latest.json holds the new version.
- Very specific: line 29
If the Apple secrets exist (gh secret list | grep APPLE): check the notarization of the arm64 .dmg (see docs/apple-notarization.md, step 7).
“Common” is measured: kept by at least 6 in 10 of the 183 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
Release PR Radar
Flow: everything goes through dev; merging the dev → main PR triggers release.yml, which publishes if the package.json version has no release yet (otherwise nothing).
- Prerequisites:
devclean and up to date, norelease.ymlrun in progress (gh run list --workflow release.yml --limit 3). One release at a time. The Slack app Redirect URLs (api.slack.com → OAuth & Permissions) must includehttps://vlor999.github.io/pr-radar/oauth.html(prradar://oauthwas removed: Slack sign-in fails before v0.6.3). - Checks:
npm run typecheck && npm test && (cd src-tauri && cargo clippy -- -D warnings && cargo test). - Bump the same
X.Y.Zversion in:package.jsonsrc-tauri/tauri.conf.jsonsrc-tauri/Cargo.toml([package] version) thennpm install --package-lock-only(andcargo checkinsrc-tauriforCargo.lock). InCHANGELOG.md, move the[Unreleased]entries into a new## [X.Y.Z] - YYYY-MM-DDsection (today's date), leave## [Unreleased]empty, and update the compare links at the bottom ([Unreleased]→vX.Y.Z...HEAD, new[X.Y.Z]→vPREV...vX.Y.Z). This section is the release notes:release.ymlfails without it, and thechangelogCI job blocks thedev → mainPR. Check:scripts/changelog-section.sh X.Y.Z.
- Commit
chore: release vX.Y.Zondev(version bump andCHANGELOG.mdtogether), with the Co-Authored-By trailer. - Confirm with the user before pushing (public action), then:
No manual tag:git push origin dev gh pr create --base main --head dev --title "chore: release vX.Y.Z" --body "..." gh pr checks --watch && gh pr merge --merge # merge commit, no squash (otherwise dev and main diverge)tauri-actioncreates thevX.Y.Ztag and the release. - Follow:
gh run watch $(gh run list --workflow release.yml --limit 1 --json databaseId -q '.[0].databaseId'). All 6 builds (macOS arm64/x64, Windows x64/arm64, Linux x64/arm64) must be green.updater-urlsandhomebrewrun even when a build fails (warning on missinglatest.jsonplatforms): re-run the failed leg (gh run rerun --failed) before announcing the release. - Check the release:
gh release view vX.Y.Z→ assets present,latest.jsonholds the new version. The Slack return page answers 200:curl -so /dev/null -w '%{http_code}' https://vlor999.github.io/pr-radar/oauth.html. - If the Apple secrets exist (
gh secret list | grep APPLE): check the notarization of the arm64.dmg(seedocs/apple-notarization.md, step 7).
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.

