repo-reviewlisted

# repo-review `orient-repo` maps a repo so you can work in it. `repo-review` judges it: where the structure fights the reader, where the docs say things the code does not do, where tests are thin, what is dead, and what has drifted. The widest review lens in the kit. Its findings feed `triage`. ## When to use it - You are taking ownership of a repo and need its true state, not its README's claims. - Before a release, an audit, or a handoff that must survive scrutiny. - On a schedule, as a health check that catches drift while it is cheap to fix. - With the ownership lens, when a repo built by one person is gaining a second contributor, a team, or a public audience, or before transferring ownership or open-sourcing. - Skip it when one change needs review; that is `code-review`. Skip it when you only need a map; that is `orient-repo`. ## Required inputs - The repo root, readable. - What done means for this repo: its stated gate (build, tests, checks), if one exists. - Optional: focus areas to weight, and areas to skip (generated code, vendored trees). - For the ownership lens: the allowed homes for personal traces (git history, CODEOWNERS, append-only ledgers). - Where the output goes: the conversation by default, or a file the caller names. - The review is read-only on the repo; running its stated gate is the only execution. ## Steps 1. Run the repo's own gate first. A red gate is finding number one; note it and continue on the tree as it stands. 2. Structure p