audit-performance

You can identify performance issues by running a structured code audit that applies P0, P1, and P2 checks to specified files or features, outputting machine-readable findings and actionable fixes.

The best way to monitor code quality during implementation is using a background audit mode that continuously checks for performance issues and injects P0 findings to the main agent for immediate remediation.

You can audit code performance on specific files by invoking the standalone audit mode on the target files, which categorizes and triages critical and performance-related problems into machine-readable outputs.

Yes, you can automate performance optimization checks by running the audit in a background mode during implementation, ensuring P0, P1, and P2 checks are applied without interrupting your build process.

Triageing performance findings into P0, P1, and P2 priority levels ensures that critical slowdowns and memory pressure issues are categorized properly, allowing P0 findings to be injected for immediate remediation.

Yes, the performance audit works entirely standalone without external debugging or monitoring dependencies, applying its internal checks directly to your codebase during or after implementation.