audit

You can audit project health by executing predefined or custom rules that check code quality, security vulnerabilities, test coverage, and CLAUDE.md documentation structure. The process supports individual or sequential combined reviews for comprehensive readiness validation.

A project structure audit evaluates documentation presence, specifically checking CLAUDE.md files, and verifies Git hygiene. It assesses the foundational project health to ensure structural standards are met before production deployment or significant feature merging.

Yes, you can execute code audits using custom rules to analyze security vulnerabilities and test coverage. The system leverages Bash, Grep, and Glob tools for rule discovery and execution, reporting specific code quality issues based on your defined standards.

You need CLAUDE.md restructuring when optimizing and standardizing project documentation fails to meet defined structure requirements. A specific audit checks this file's organization to ensure it aligns with expected documentation standards before merging features.

Yes, the audit supports a full sequential review mode that runs project, code, and CLAUDE.md checks back-to-back. This combined approach provides a comprehensive assessment of overall project health and code quality in one execution.

Using Bash, Grep, and Glob tools for code quality audits means the system relies on pattern matching and shell commands rather than deep semantic analysis. This approach is limited to discovering and executing predefined rules without runtime behavioral testing.