release
Skill8 starsChanged 9 months agoMITView on GitHub
Evaluate and execute a release with version bump, changelog, tag, and GitHub release
- Commits and pushes
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
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
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 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
parcadeiSkillagent-context-isolation
Agent Context Isolation
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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/consolidation-memory.mdcCursor rule
- reviewSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
5
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 12
If $ARGUMENTS is empty, evaluate whether a release is warranted:
- Distinctive: line 20
If warranted, recommend a version number and ask for confirmation
- Distinctive: line 21
If not warranted, explain why and stop
- Distinctive: line 27
Verify working tree is clean: git status --porcelain
- Very specific: line 29
Read current version from pyproject.toml
- Very specific: line 31
Read CHANGELOG.md and the commits since last tag
- Distinctive: line 32
Write a changelog entry for the new version matching the existing format:
- Very specific: line 38
If tests/lint pass, commit: git add pyproject.toml CHANGELOG.md && git commit -m "v$ARGUMENTS"
- Very specific: line 41
Create GitHub release: gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-from-tag
- Distinctive: line 43
If tests or lint fail, stop and report the failures.
“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 consolidation-memory
If No Version Argument
If $ARGUMENTS is empty, evaluate whether a release is warranted:
- Find the latest git tag:
git describe --tags --abbrev=0 - List commits since that tag:
git log <tag>..HEAD --oneline - Categorize changes (features, fixes, refactors, docs, tests)
- Apply release criteria:
- Release: new features, noteworthy bug fixes, pre-refactor checkpoint
- Skip: internal refactors only, test-only, docs-only, minor tooling
- If warranted, recommend a version number and ask for confirmation
- If not warranted, explain why and stop
If Version Provided
Execute release for version $ARGUMENTS:
- Verify working tree is clean:
git status --porcelain - Pull latest:
git pull --ff-only origin main - Read current version from
pyproject.toml - Bump version in
pyproject.tomlto$ARGUMENTS - Read
CHANGELOG.mdand the commits since last tag - Write a changelog entry for the new version matching the existing format:
- Date: today's date (YYYY-MM-DD)
- Sections as appropriate: Features, Bug Fixes, Refactoring, Performance, Security, Documentation, Internal
- Include test count if it changed
- Run tests:
python -m pytest tests/ -v - Run linter:
python -m ruff check src/ tests/ - If tests/lint pass, commit:
git add pyproject.toml CHANGELOG.md && git commit -m "v$ARGUMENTS" - Tag:
git tag v$ARGUMENTS - Push:
git push origin main && git push origin v$ARGUMENTS - Create GitHub release:
gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-from-tag
If tests or lint fail, stop and report the failures. Do NOT commit broken code.
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.

