release
Skill2 starsChanged 8 months agoMITView on GitHub
Release a new Prismstack version. Runs tests, updates changelog, bumps version, tags, reinstalls globally. Trigger: "release", "ship", "bump version", "new version" Do NOT use when: still making changes (finish first, then release)
196 other projects use a version of this.
Adopted by
Most recently taken up by
- zxcvbn-ts/zxcvbntheir own version, first seen Nov 9, 2026
- TechbeeAT/jtxBoardtheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- zerx-lab/FluxDowntheir own version, first seen Nov 9, 2026
- orioledb/orioledbtheir own version, first seen Nov 9, 2026
- AmruthPillai/Reactive-Resumetheir own version, first seen Nov 8, 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 versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- paperclipai/paperclip★ 112ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 72ksame name
- traefik/traefik★ 65ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 63ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- amruthpillai/reactive-resume★ 45ksame name
- reactive-resume/reactive-resume★ 45ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
186 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.
- CLAUDE.mdCLAUDE.md
- dogfoodSkill
- methodology-syncSkill
- self-checkSkill
- skill-devSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
All tests must pass (expect 67/67).
- Distinctive: line 31
Must be clean (no uncommitted changes).
- Distinctive: line 49
Read the current version:
- Very specific: line 55
Read CHANGELOG.md for any unreleased section.
- Distinctive: line 60
fix: only → patch bump (0.5.0 → 0.5.1)
- Distinctive: line 66
Do NOT continue without user confirmation.
- Very specific: line 72
Write the new version string (just the number, no v prefix).
- Distinctive: line 76
Add a new version header at the top of the changelog (below any title):
- Distinctive: line 130
If anything failed, report exactly what and at which phase.
“Common” is measured: kept by at least 6 in 10 of the 186 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
<!-- Internal maintenance skill — edit this file directly -->/release: Ship a New Prismstack Version
You are the release manager. You ensure every release is tested, documented, tagged, and installed.
Phase 1: Pre-Flight Checks
Run tests
bash test/install-test.shAll tests must pass (expect 67/67). If any fail, stop and report: "Cannot release — N test failures. Fix first."
Check working tree
git status --shortMust be clean (no uncommitted changes). If dirty, stop and report: "Cannot release — uncommitted changes found. Commit or stash first."
Review changes since last release
git describe --tags --abbrev=0 2>/dev/null || echo "no-tags"Then show commits since that tag:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEADSummarize the changes by category: features, fixes, docs, refactors.
Phase 2: Determine Version Bump
Read the current version:
cat VERSIONRead CHANGELOG.md for any unreleased section.
Apply semantic versioning:
- breaking: changes → major bump (0.5.0 → 1.0.0)
- feat: changes → minor bump (0.5.0 → 0.6.0)
- fix: only → patch bump (0.5.0 → 0.5.1)
Present the proposed version and changelog to the user. Ask for confirmation before proceeding:
"Proposed release: vX.Y.Z with these changes: [summary]. Proceed?"
Do NOT continue without user confirmation.
Phase 3: Update Files
VERSION file
Write the new version string (just the number, no v prefix).
CHANGELOG.md
Add a new version header at the top of the changelog (below any title):
## [X.Y.Z] - YYYY-MM-DD
### Added
- feat: description (from commit messages)
### Fixed
- fix: description
### Changed
- refactor: descriptionOrganize commits under the appropriate heading. Drop trivial commits (typo fixes, etc.) unless they are the only changes.
Phase 4: Commit and Tag
git add VERSION CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.ZVerify the tag:
git tag --list | tail -5Phase 5: Reinstall Globally
bash bin/install.sh --globalVerify installation:
ls ~/.claude/skills/prismstack/Confirm the installed skills match the released version.
Output
Report:
- Version: vX.Y.Z
- Changes: summary of what shipped
- Tests: 67/67 passed
- Tag: created
- Install: confirmed at
~/.claude/skills/prismstack/
If anything failed, report exactly what and at which phase.
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.

