repo-auditor

To audit a git repository, scan files and git metadata to detect frameworks, tests, and pipelines, then generate a persistent markdown index mapping stack, conventions, and risks. This creates a concise operational snapshot for onboarding or pre-feature planning.

Codebase audit documentation is a persistent markdown snapshot mapping repository stack, assets, and integration points. You need it during initial onboarding, before major migrations, or when actual stack diverges from reference templates to prioritize next steps.

Yes, repository risk assessment works on web, backend, and monorepo projects. It reads repository files and git metadata to detect conventions and generate focused split files for routes, schema, components, services, and infrastructure only when relevant.

The best way to document conventions and integration points is generating a persistent indexed markdown file at docs/repo-audit/current.md. This reduces re-reads and token usage by creating focused split files only when relevant changes are detected.

Detect framework and test suite usage by scanning repository files and git history for automatic discovery. This identifies tooling, pipelines, and visual assets, producing a concise operational snapshot for downstream automation and human action.

Limitations include updating audits only when relevant changes are detected to maintain token-efficiency. The process generates focused split files for schema, components, or infra strictly when relevant, avoiding unnecessary re-reads across web, backend, and monorepo projects.