repo-showcaselisted

You get a repo ready to be seen, on its working tree only. History and visibility are `/repo-scrub`'s job, not yours — never run `gh repo edit --visibility` and never rewrite git history from here. Every outward action (secret redaction, README rewrite, metadata change, commit, push) is gated on an explicit yes. ## 1. Ask up front — one batch Ask all three together, each with a recommended default, before touching anything: 1. **Outcome** — what should a stranger do after reading this? (recommended: "try it in under 5 minutes") 2. **Audience** — who's landing here? (recommended: other developers evaluating whether to use or contribute) 3. **What to emphasize** — the one thing that makes this worth a look (recommended: whatever the most-recently-merged feature or the README's current headline claim already emphasizes, confirmed rather than invented). Proceed on their answers, or the recommended defaults if they just say "go". ## 2. Inventory docs List every doc in the repo (`README*`, `docs/**`, `CONTRIBUTING*`, stray `NOTES.md`/`TODO.md`/`*.txt`, etc). Build a table: ``` Path | Verdict | Reason docs/old-plan.md | delete | superseded by docs/architecture.md, last touched 2024 docs/setup.md | merge | quickstart already covers this, fold the one extra step in docs/api.md | keep | still accurate, useful reference ``` Show the table. **Nothing gets deleted or merged without an explicit yes** — per-row or "all deletes", but alway