release-prep — Claude Code skill: audit, fixes, release PR
Runs a full audit, fixes critical bugs, validates deploy readiness and writes the release PR. Useful right before shipping a version to production.
npx skills add undeadlist/claude-code-agents --skill release-prep -a claude-codeWhat release-prep does
The skill works through six phases. Eleven audit agents run in parallel first, each dropping a report into .claude/audits/AUDIT_*.md. Then fix-planner reads those reports and writes a prioritized task list to .claude/audits/FIXES.md.
code-fixer handles the code changes, and only P1 ones. P2 and P3 wait for a later release, so this will not clear your whole backlog. After that test-runner runs the test suite and watches for regressions, while deploy-checker looks at the build, the environment and dependencies. pr-writer closes the run by assembling a release PR with the audit findings and the fixes that landed.
A release stays blocked while any P1 issue is open, tests fail or the build breaks. The should-pass items — P2 work, performance, docs — can be documented and pushed to the next cycle. You can pass a version and a release date to the command, and both end up in the PR text.
What it helps with
- run a full audit before shipping a version
- turn audit reports into a prioritized fix list
- patch only critical P1 bugs and leave the rest
- check that fixes did not break the test suite
- confirm the build and environment are ready to deploy
Example prompts for the agent
- Run
/release-prepfor version 2.1.0 - Prep the release: audit, critical fixes, deploy check and PR
- Run
/release-prepand show me which P1 issues are still open
How to install release-prep
1Skills CLI (Vercel)
npx skills add undeadlist/claude-code-agents --skill release-prep -a claude-code2Manually: put the files in place
~/.claude/skills/release-prep/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-prep/
1Skills CLI (Vercel)
npx skills add undeadlist/claude-code-agents --skill release-prep -a codex2Manually: put the files in place
.agents/skills/release-prep/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add undeadlist/claude-code-agents --skill release-prep -a cursor2Manually: put the files in place
.cursor/skills/release-prep/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install undeadlist/claude-code-agents release-prep2Manually: put the files in place
.github/skills/release-prep/SKILL.md1Skills CLI (Vercel)
npx skills add undeadlist/claude-code-agents --skill release-prep -a gemini-cli2Platform CLI
gemini skills install https://github.com/undeadlist/claude-code-agents --path skills/release-prepManually: put the files in place
.devin/skills/release-prep/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add undeadlist/claude-code-agents --skill release-prep -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-prep
How do I install release-prep in Claude Code?
Run npx skills add undeadlist/claude-code-agents --skill release-prep -a claude-code. The skill file lands at ~/.claude/skills/release-prep/SKILL.md.
What does release-prep do?
It audits the project, plans the fixes, applies critical P1 changes, runs the tests, validates deploy readiness and generates the release PR.
What blocks a release?
Any remaining P1 issue, failing tests, a broken build or a failed deploy check. P2 items can be documented and deferred to the next release.
Source text
SKILL.md · MIT
--- name: release-prep description: Full audit + fixes + deploy validation for production release --- # Release Prep Workflow Prepare for a production release. Runs full audit, fixes critical issues, validates deployment readiness, and generates the release PR. ## Execution (Sequential Phases) ### Phase 1: Full Audit (Parallel) Spawn all 11 audit agents in parallel (same as `/full-audit`): - All auditors save reports to `.claude/audits/AUDIT_*.md` ### Phase 2: Fix Planning Spawn `fix-planner`: - Read all audit reports - Create `.claude/audits/FIXES.md` with prioritized action items ### Phase 3: Critical Fixes Spawn `code-fixer`: - Implement **P1 (critical) fixes only** - P2/P3 can wait for next release ### Phase 4: Verification Spawn `test-runner`: - All tests pass (including after fixes) - No regressions introduced ### Phase 5: Deploy Validation Spawn `deploy-checker`: - Build succeeds - Environment valid - Dependencies clean ### Phase 6: PR Generation Spawn `pr-writer`: - Generate release PR with summary of all changes - Include audit findings and fixes applied ## Release Criteria ### Must Pass (Blockers) - Zero P1 issues remaining - All tests pass - Build succeeds - Deploy checker passes ### Should Pass (Document if not) - P2 issues addressed or documented - Performance within acceptable range - Documentation updated ## Usage ``` /release-prep Version: 2.1.0 Release date: 2024-03-15 ```
© undeadlist · MIT · undeadlist/claude-code-agents
