release-readinesslisted

# Release Readiness Skill Run a final go/no-go gate before cutting a release. This skill inspects the repository itself — the commits, changed files, changelog, version files, and CI config since the last release — and produces an evidence-backed verdict. It does not take the author's word for anything: a gate is rated PRESENT only when the evidence is found, MISSING otherwise. The output is a single verdict — **GO**, **CONDITIONAL**, or **NO-GO** — plus the exact list of blocking items when it is not a clean GO. ## Step 1: Establish the Release Context Run the scan script to gather raw facts about what is being shipped: ```bash ~/.claude/skills/release-readiness/scripts/scan-release.sh ``` This reports: the last release tag, commits and changed files since that tag, any uncommitted changes, detected CHANGELOG and version files, CI config presence, and any leftover TODO / FIXME / debug markers in the changed files. If the user passed a target version or git-ref as an argument, treat that as the release under evaluation. If the working tree is dirty, note it — a release cut from a dirty tree is itself a CONDITIONAL at best. ## Step 2: Determine the Release Type Pick the path that applies — it changes which gates are mandatory: - **Standard release** — planned minor/major/patch of a library or service. Full gate set. - **Emergency hotfix** — urgent fix to a live incident. Follow `~/.claude/skills/release-readiness/runbooks/HOTFIX.md` for the reduced gate set. If it i