release-captain
Skill1 starsChanged 5 months agoMITView on GitHub
Prepare software releases, changelogs, release notes, semantic version decisions, migration notes, publish checklists, and GitHub release drafts. Use when the user asks to cut a release, tag a version, publish a package, summarize changes since the last release, or verify release readiness. Do not use for unrelated marketing copy or routine docs edits.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Check readiness: tests, build, docs, migrations, compatibility, security notes, and rollback path.
- Distinctive: line 17
Do not publish, tag, or mutate package registries unless the user explicitly approves that final action.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Captain
Make releases boring, traceable, and reversible.
Workflow
- Identify the release target, previous tag, versioning scheme, package names, and publish destination.
- Compare commits since the previous release and group changes by user impact.
- Check readiness: tests, build, docs, migrations, compatibility, security notes, and rollback path.
- Decide version bump from public API or user-visible behavior, not commit count.
- Draft release notes with install/upgrade instructions.
- Do not publish, tag, or mutate package registries unless the user explicitly approves that final action.
Release Notes Shape
Title:
Summary:
Highlights:
Breaking changes:
Migration notes:
Fixes:
Verification:
Rollback:
Links:Checklist
- Version number matches project conventions.
- Changelog and README links are current.
- Generated artifacts are intentionally included or ignored.
- Package lockfiles match manifests.
- CI or local verification is recorded.
- Secrets and local paths are absent from notes.
- Release URL, tag, and commit SHA are captured after publishing.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NVIDIA/OpenShell★ 21ksame name
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 repository11 other files it gives its agents.
- docs/llms.txtllms.txt
- llms.txtllms.txt
- docs-keeperSkill
- frontend-polisherSkill
- issue-sherpaSkill
- migration-pilotSkill
- perf-labSkill
- pr-reviewerSkill
- real-engineerSkill
- repo-cartographerSkill
- security-scoutSkill
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.