Release Checklist Sequential release gate for OrchestKit. Each step reports [PASS] or [FAIL] . Stop on first failure, suggest a fix, then continue after user confirmation. Load details: Read("${CLAUDE_PLUGIN_ROOT}/skills/release-checklist/references/release-flow.md") for why the order matters and hotfix guidance. Quick Reference Category Rules Impact When to Use Pre-Release Gates 2 CRITICAL Before every release commit Release Commit 2 HIGH Staging, committing, tagging, pushing Total: 4 rules across 2 categories Quick Start
Run all pre-release gates in order (stop on first failure)
npm run build && npm test && npm run test:security && npm run typecheck bash src/skills/validate-counts/scripts/validate-counts.sh git diff
review before staging
Pre-Release Gates
Must all pass before writing any release commit. See
rules/gate-build-and-test.md
and
rules/gate-counts-and-diff.md
.
Step
Command
Rule File
1. Build
npm run build
rules/gate-build-and-test.md
2. Tests
npm test
rules/gate-build-and-test.md
3. Security
npm run test:security
rules/gate-build-and-test.md
4. TypeScript
npm run typecheck
rules/gate-build-and-test.md
5. Validate counts
/validate-counts
rules/gate-counts-and-diff.md
6. Diff review
git diff
rules/gate-counts-and-diff.md
Release Commit
Steps after all gates pass. See
rules/commit-staging.md
and
rules/commit-tag-push.md
.
Step
Action
Rule File
7. Changelog
Entry exists in
CHANGELOG.md
rules/commit-staging.md
8. Version bump
package.json
+
CLAUDE.md
both updated
rules/commit-staging.md
9. Stage files
git add