release
Skill69 starsChanged 39 days agoMITView on GitHub
Release the go-qr library, and the tools and mcp modules that follow it, through the release pull request, the release workflow and Dependabot. Use only when a maintainer asks for a release.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 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
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame 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.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- perf-checkSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read ## [Unreleased] in CHANGELOG.md.
- Very specific: line 21
Check the open pull requests (gh pr list).
- Very specific: line 23
Make sure the last CI run on main passed: gh run list --branch main -L 3.
- Very specific: line 27
Run scripts/release.sh without arguments.
- Very specific: line 34
Run scripts/release.sh X.Y.Z.
- Very specific: line 38
Wait for CI (gh pr checks <number> --watch).
- Distinctive: line 65
Do not create tags or releases by hand, and do not edit the tag rules.
“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
Releases are made by .github/workflows/release.yml; tags are protected
and a hook blocks creating them by hand. This skill prepares and checks the
pull requests that trigger the workflow. The steps are in
CONTRIBUTING.md.
1. Check that main is ready
git checkout main && git pull, with a clean working tree.- Read
## [Unreleased]inCHANGELOG.md. Every user-visible change since the last tag (git log --oneline $(git tag -l 'v*' | sort -V | tail -1)..HEAD) must have an entry. Report missing or unclear entries to the maintainer instead of releasing. - Check the open pull requests (
gh pr list). Ask whether any should go into this release. - Make sure the last CI run on main passed:
gh run list --branch main -L 3.
2. Choose the version
Run scripts/release.sh without arguments. It prints the suggested version:
minor for Added, Changed, Deprecated or Removed entries, patch otherwise.
Tell the maintainer the suggestion and the reason, and wait for their
choice. Never release a new major version; that needs a new module path.
3. Open the release pull request
Run scripts/release.sh X.Y.Z. It checks the version and the docs'
Since markers, moves the entries under the new heading, and opens
chore: release vX.Y.Z. If it refuses, report why; do not work around it.
Wait for CI (gh pr checks <number> --watch). Merge only when the
maintainer says so: gh pr merge <number> --squash --delete-branch.
4. Confirm the release
- Watch the workflow:
gh run list --workflow=release.yml -L 1, thengh run watch <id>. - Confirm the release exists (
gh release view vX.Y.Z) and that the module proxy has it:GOPROXY=https://proxy.golang.org GOWORK=off go list -m github.com/piglig/go-qr/v2@vX.Y.Z.
5. tools and mcp
Dependabot checks daily and opens chore(deps): bump github.com/piglig/go-qr/v2 ...
for /tools and /mcp. When it appears, check that CI passes, including
test (tools and mcp on the pinned library), and merge it when the
maintainer agrees. The workflow then releases the next patch versions of
tools and mcp, or the next minor version of a module whose pin changes
in a feat pull request; confirm them as in step 4.
To release tools or mcp without a library release, for example for a
new CLI flag, the maintainer runs the release workflow by hand from the
Actions tab (gh workflow run release.yml -f module=tools -f bump=minor),
after confirming the version with them.
If something fails
Do not create tags or releases by hand, and do not edit the tag rules. Report the failing step and its log to the maintainer.
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.

