Repo Health Check
You just landed in a repo. Become useful in one pass.
Report these, in order
- What it is — one paragraph, no marketing.
- How to run it — the actual command from the README or package scripts. Run a cheap check if you can (
--help, typecheck, unit subset). - Layout — the 8–12 paths that matter, not a tree dump.
- Invariants — auth, data, build, deploy. Quote the file that enforces each.
- Risks — untested money/auth paths, generated files checked in, secrets, flaky scripts.
- First safe change — the smallest useful edit that will not require a rewrite.
Do not
- Propose a reorg on sight.
- List every TODO.
- Claim tests pass if you did not run them.