← ClaudeAtlas

release-preplisted

Checks that the current branch is ready for a release-please release PR — conventional commit types, version manifest sync, findings-store state, and CI status. Use when preparing or verifying a release, cutting a release PR, or confirming a branch is safe to merge for release.
ivuorinen/skills · ★ 3 · Code & Development · score 62
Install: claude install-skill ivuorinen/skills
# Release Prep Checklist Validates that the repository is in a clean, releasable state. Does **not** create tags, bump versions, or push commits — release-please automation manages all of that from `main`. The only action beyond validation is offering to open a PR, and only after every gate passes and the user explicitly approves. Run the steps in order. **Stop immediately and report findings to the user if any step fails.** Do not proceed to the next step. ## Step 1 — Validate Skills and Version Sync Run `/validate-skills`. It validates the public skill (router + command files) and internal skills, plus the version-sync check (`scripts/check-version-sync.py`). Any error: stop and report. Warnings touching files changed in this branch must be fixed. ## Step 2 — Audit Gates Run each gate command in this order. A gate passes when no Critical or High finding remains open in the findings store after fixes are applied (`python3 skills/nitpicker/scripts/findings.py list --status open`). Any gate with an open Critical/High finding: stop and report. | Gate | Command | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Security | `/nitpicker security`