ワンクリックで
release-checklist
Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed.
メニュー
Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed.
| name | release-checklist |
| description | Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed. |
| tools | Read, Grep, Glob, Bash |
| user-invocable | true |
A final quality gate before shipping code. This skill runs through everything a senior developer would check before approving a release.
/release-checklist
Or specify a scope:
/release-checklist src/auth/
Run through each section systematically. Any failure blocks the release.
# Search for incomplete code markers
grep -r "TODO\|FIXME\|XXX\|HACK\|WIP" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" --include="*.rs" --include="*.rb" --include="*.ex" src/
throw new Error('Not implemented'))# Search for debug statements
grep -rn "console\.log\|print(\|debugger\|binding\.pry\|byebug\|IEx\.pry" --include="*.ts" --include="*.js" --include="*.py" --include="*.rb" --include="*.ex" src/
console.log in production code (logging libraries OK)print() statements (Python)debugger statementsbinding.pry / byebug (Ruby)IEx.pry (Elixir)Run all test commands from CLAUDE.md:
# Example - adapt to your project
npm test # or pytest, go test, etc.
npm run lint # or ruff, golangci-lint, etc.
npm run typecheck # or mypy, tsc, etc.
npm run build # verify it compiles
For any new dependencies added:
# Check for outdated or vulnerable packages
npm audit # Node.js
pip-audit # Python
go list -m -u all # Go
cargo audit # Rust
bundle audit # Ruby
mix deps.audit # Elixir (with mix_audit)
## Release Checklist Results
### Passed
- [x] No TODO/FIXME markers
- [x] No debug statements
- [x] Tests passing
- [x] Lint passing
- [x] Build succeeds
### Failed
- [ ] CHANGELOG not updated (missing entry for new auth feature)
- [ ] Found console.log at src/api/users.ts:45
### Warnings
- [ ] New dependency 'lodash' added - verify it's needed (could use native methods)
### Verdict
**BLOCKED** - Fix the failures above before releasing.
When used as part of a wiggum loop, this checklist runs during Phase 5 (Final Verification). All items must pass before the loop can complete.
This checklist exists because senior developers do these checks naturally. Making them explicit ensures nothing slips through, especially in automated workflows.
If any item fails, the release is blocked. Fix the issue and run the checklist again.
Start an autonomous implementation loop from a spec or PRD. Enters plan mode for user approval, enforces command gates (test/lint/typecheck/build), validates dependencies, commits incrementally, and maintains documentation and changelog. Production-ready quality gates.
Document risks for changes touching auth, data, or migrations. Lists top risks, how to test/monitor them, and rollback strategy.
Maintain CHANGELOG.md with properly categorized entries. Use after implementing features, fixing bugs, or making any notable changes. Follows Keep a Changelog format.
Review code changes for quality, security, and best practices. Use when reviewing staged changes, pull requests, or specific files before merging.
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.
Generate comprehensive tests for code. Use when adding test coverage, implementing TDD, or ensuring code reliability.