release-captain
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
SKILL.mdskills/release-captain/SKILL.md
GitHubRelease 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.