full-project-audit

To generate a project audit report without modifying source code, run a read-only workflow that analyzes your repository against guidelines and outputs a portable audit file with a fix plan. The analysis remains non-invasive throughout the entire process.

A full project audit includes analysis of APIs, features, routes, mutations, stores, and related documentation to identify deviations from architecture rules. It produces a detailed report containing findings, a progress tracker, and a to-do list for fixes.

To check repository compliance with architecture rules and project guidelines, execute an audit workflow that scans all APIs, features, and documentation. It generates a traceable markdown report with identified deviations and a structured fix plan.

The project audit report gets saved as a markdown file at audits/audit-YYYY-MM-DD.md. This portable format contains all findings, a progress tracker, and a to-do list to ensure traceability for your project compliance checks.

Yes, you can use a read-only code quality audit to generate a fix plan and to-do list. The process performs a non-invasive analysis of your project documentation and architecture rules, saving all findings directly into a traceable markdown report.

The best way to prepare for a non-invasive repository audit is ensuring your project guidelines and architecture documentation are up to date. The audit workflow then reads these rules to evaluate APIs, features, and stores without altering source code.