What problem does it solve? Repositories accumulate stray files, missing documentation, committed secrets, and "works on my machine" gaps that make them unsafe or impossible for others to run. This Skill provides a single checkpoint that decides whether a repo is ready to publish, hand off, or release — and exactly what to fix first if it is not. ## Core Features & Use Cases - Five-Area Readiness Pass: Checks safety (secrets, private data, .gitignore), structure (no committed artifacts or vendored deps), docs (README, .env.example), dependencies (pinned manifest, lockfile), and runnability (clone-and-run from README alone). - Go / Fix-First Verdict: Returns a clear verdict with a prioritized punch list, blockers listed before nice-to-haves. - Edge-Case Handling: Adjusts the bar for private handoffs, prototypes, monorepos, and repos without tests. - Use Case: Before open-sourcing a side project, run this review to catch a committed .env file and a missing run command in the README, fix them, and then ship with confidence. ## Quick Start Review this repository for readiness before I make it public and give me a go or fix-first verdict with a prioritized punch list.