release
Skill171 starsChanged 8 months agoMITView on GitHub
Prepare a new release by updating CHANGELOG.md, verifying documentation (README.md, CLAUDE.md, AGENTS.md, ROADMAP.md, docs/), bumping patch version in package.json, building, and suggesting publish commands. Use when asked to release, bump version, prepare release, or publish.
- 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- paperclip-aiSkill
- routinesSkill
- setup-routinesSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
10
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
- Distinctive: line 53
Check each documentation file against the actual codebase.
- Distinctive: line 78
Add any new backlog items discovered during development
- Distinctive: line 79
Remove items that are no longer relevant
- Distinctive: line 87
Only update what's actually wrong or missing.
- Distinctive: line 88
If counts changed (e.g., "14 presets" → "15 presets"), update all occurrences across all files.
- Distinctive: line 89
If a new state field was added, ensure CLAUDE.md's WizardContext description mentions it.
- Distinctive: line 90
If new worker actions were added, ensure they're listed in the architecture section.
- Distinctive: line 102
Also check: if the version appears in any other files (README badges, etc.) and update those too.
- Distinctive: line 111
If any step fails, fix the issue before proceeding.
- Distinctive: line 115
Do NOT run these commands — just print them for the user to review and execute manually.
- Very specific: line 137
If the package is scoped (starts with @), remind the user that --access public is needed for public packages.
“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 — Prepare and Document a New Version
Phase 1: Analyze Changes
Understand what changed since the last release:
- Read current version from
package.json. - Read
CHANGELOG.mdto understand the last documented version and its date. Note any gap — ifpackage.jsonis ahead of the changelog, intermediate releases were shipped without entries. - Find the release boundary. Try
git tag -l 'v*' --sort=-v:refname | head -5for the latest tag. If no tags exist, find the commit that last bumped the version (e.g.,git log --oneline --all -- package.json | head -5) and use that SHA as the base. - Run
git log <base>..HEADto collect all commit messages since the last release. - Run
git diff <base>..HEADto see all committed file changes. Also rungit diff HEADto capture any uncommitted work in the working tree — this may contain unreleased feature work. - Count templates from the filesystem to verify against documentation:
ls templates/presets/ | wc -lls templates/modules/ | wc -lls templates/roles/ | wc -l
- Pay attention to:
- New features (new files, new actions, new UI steps)
- Bug fixes (error handling, logic corrections)
- Template changes (new presets, modules, roles, prompt updates)
- Configuration changes (new settings, defaults)
- Breaking changes (removed features, renamed fields, API changes)
- Categorize changes into: Added, Changed, Fixed, Removed, Template system (if applicable).
Phase 2: Update CHANGELOG.md
- Read
CHANGELOG.mdto understand the existing format and style. - If intermediate versions exist without changelog entries (e.g.,
package.jsonjumped from 0.1.0 to 0.1.2 but the changelog only has 0.1.0), create brief entries for the skipped versions too — even if they were just version bumps or metadata changes. Add a new version section at the top (below the header), following Keep a Changelog format:
## [X.Y.Z] — YYYY-MM-DD ### Added - Feature description ### Changed - Change description ### Fixed - Bug fix description- Match the tone and detail level of existing entries. Be specific — mention file names, action names, field names where relevant.
- Do NOT include trivial changes (formatting, comments) unless they affect behavior.
Phase 3: Verify Documentation
Check each documentation file against the actual codebase. For each file, read it and verify accuracy. Only edit if something is factually wrong or missing due to the changes being released.
Files to check
README.md— Verify:- Feature descriptions match current behavior
- Configuration options are up to date
- Template counts (presets, modules, roles) are accurate
- Example commands still work
- Any new features from this release are mentioned where appropriate
CLAUDE.md— Verify:- Architecture description matches current source layout
- Key concepts are accurate (especially if state fields, actions, or API flow changed)
- Template system description is current
- Build/test commands are correct
AGENTS.md— Verify:- Project vision still matches reality
- Architecture diagram is current
- Design principles haven't been violated by changes
- Template/module/role counts are accurate
ROADMAP.md— Verify:- Move newly completed items from "Backlog" or "In Progress" to "Done"
- Add any new backlog items discovered during development
- Remove items that are no longer relevant
docs/directory — Verify:- Any documentation files are consistent with template/module changes
- Cross-references between docs are still valid
Documentation rules
- Only update what's actually wrong or missing. Don't rewrite prose that's still accurate.
- If counts changed (e.g., "14 presets" → "15 presets"), update all occurrences across all files.
- If a new state field was added, ensure CLAUDE.md's WizardContext description mentions it.
- If new worker actions were added, ensure they're listed in the architecture section.
Phase 4: Bump Version
You MUST bump the version. Do NOT skip this phase. Do NOT leave the version unchanged.
- Read
package.jsonto get the current version. - Check for recent version-bump commits — run
git log --oneline -5 -- package.jsonto ensure you're not colliding with a version that was already bumped externally. If the current version was bumped by a recent commit you haven't accounted for, increment from that version instead. - Increment the patch version (e.g.,
0.1.5→0.1.6). Always patch. Never minor or major unless the user explicitly says so. - Edit
package.json— change the"version"field to the new version. - Edit
src/manifest.ts— change theversionfield to the same new version. - Verify both files match — grep both files to confirm the version is identical.
- Also check if the version appears in any other files (README badges, etc.) and update those too.
Phase 5: Build and Verify
- Run
pnpm build— ensure it succeeds with no errors. - Run
pnpm typecheck— ensure no type errors. - Run
pnpm test— vitest plugin tests. - Run
pnpm test:logic— node:test logic suite. Both test suites must pass.
If any step fails, fix the issue before proceeding.
Phase 6: Suggest Publish Commands
Do NOT run these commands — just print them for the user to review and execute manually.
Present the commands in order:
# Review the changes one more time:
git diff
# Commit everything:
git add -A
git commit -m "chore: release vX.Y.Z"
# Tag the release:
git tag vX.Y.Z
# Push:
git push && git push --tags
# Publish to npm:
pnpm publish --access publicIf the package is scoped (starts with @), remind the user that --access public is needed for public packages.
Also mention: "After publishing, reload the plugin in the Paperclip UI to pick up the new version."
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.

