release-checklist

> **Explicit invocation only**: This skill should only run when the user explicitly requests it with `/release-checklist`. Do not auto-invoke based on context matching. ## Phase 1: Parse Arguments Read the argument for the target platform (`pc`, `console`, `mobile`, or `all`). If no platform is specified, default to `all`. --- ## Phase 2: Load Project Context - Read `CLAUDE.md` for project context, version information, and platform targets. - Read the current milestone from `production/milestones/` to understand what features and content should be included in this release. --- ## Phase 3: Scan Codebase Scan for outstanding issues: - Count `TODO` comments - Count `FIXME` comments - Count `HACK` comments - Note their locations and severity Check for test results in any test output directories or CI logs if available. --- ## Phase 4: Generate the Release Checklist ```markdown ## Release Checklist: [Version] -- [Platform] Generated: [Date] ### Codebase Health - TODO count: [N] ([list top 5 if many]) - FIXME count: [N] ([list all -- these are potential blockers]) - HACK count: [N] ([list all -- these need review]) ### Build Verification - [ ] Clean build succeeds on all target platforms - [ ] No compiler warnings (zero-warning policy) - [ ] All assets included and loading correctly - [ ] Build size within budget ([target size]) - [ ] Build version number correctly set ([version]) - [ ] Build is reproducible from tagged commit ### Quality Gates - [ ] Zero S1 (Critic...