Auditing Repository Health

Overview

Run a read-only repository health audit before trusting a repo for repeated work. The script is the executable baseline; references provide judgement for repo topology and ecosystem setup.

Required Workflow

1. Run the bundled auditor first.
2. Read the generated Repository Inventory and Lifecycle Gate Matrix.
3. Classify the repository before writing findings.
4. Read references/report-contract.md.
5. Read references/repo-foundation-rubric.md when recommending foundations.
6. Use references/ecosystem-index.md to choose only the relevant ecosystem overlays.
7. Inspect Folder Structure before recommending file moves, cleanup, or repo tree changes.
8. For monorepos and polyrepos, assess root/shared foundations separately from each package, service, app, docs root, or mirror root.
9. Preserve the existing report sections and add the inventory/classification sections when applicable.
10. Do not prescribe generic boilerplate, generic repo trees, or Scripts-to-Rule-Them-All filenames unless evidence shows that convention already fits the repo.
11. Every finding must name the affected path or scope and cite concrete evidence.