archivist-readability-auditor

Run a static analysis pass over your codebase to identify readability problems like long files, unclear identifiers, nested logic, and mixed responsibilities, generating standardized reports under the code-audits directory.

Long files, unclear names, deeply nested logic, mixed responsibilities, hard-to-scan components, missing or outdated comments, magic numbers, and unclear control flow are common readability problems that slow development in large repositories.

Yes, you can generate maintainability reports without modifying source code by running a report-only audit that stores findings with precise source file references under the docs/code-audits/reports/ directory.

Track code quality findings by generating standardized FINDING IDs in the READ-### format, stored alongside precise source file references in reports under the docs/code-audits/reports/ directory.

Yes, this readability audit applies to large repositories requiring maintainability audits and specifically targets mixed responsibilities, deeply nested logic, and long files to surface issues and speed up development.

Run a focused readability audit that flags unclear names for files, functions, variables, and components, and identifies magic numbers, producing a standardized report to support documentation and refactoring.