rollback-readinesslisted

Score how safely a project can be deployed AND rolled back — the final pre-push check. Use whenever the user says they're about to deploy, ship, launch, or push to production, asks 'is this ready to deploy', finishes a feature destined for prod, or at the end of any session that produced deployable changes. Run this proactively; it is the capstone check of the preflight pack. Runs fully offline — no API keys, no network, no credentials.
Starr-del/ShipSafe · ★ 0 · DevOps & Infrastructure · score 70

Install: claude install-skill Starr-del/ShipSafe

# rollback-readiness Part of **shipsafe** — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine. ```bash python3 scripts/readiness.py <project_root> [--json] ``` Runs 8 weighted checks and emits PASS/WARN/FAIL per check plus a 0–100 readiness score: health endpoint exists · env documented in .env.example · lockfile committed · migrations reversible · no committed secrets (quick pass) · runtime version pinned · deploy CI has concurrency control · README has run/deploy instructions. Score bands: ≥80 ready · 60–79 fix FAILs first · <60 deploying now means debugging in production. This skill is the entry point to the rest of the pack — each FAIL maps to a deeper skill (secrets → secret-preflight, migrations → migration-reversibility, env → env-drift, CI → ci-workflow-doctor). Run the deep skill on whatever fails, fix, and rerun until the score clears 80. The framing to give the user: the score measures whether the person paged at 2am — possibly future-you — can understand, redeploy, and roll back this project without you in the room. Exit codes: 0 score ≥ 80, 1 below. All paths below are relative to this skill's directory (rollback-readiness/).