audit

Project audits combine code quality, design, security, and documentation checks into a structured report. Execute /audit to perform a full project-wide scan that evaluates TypeScript strictness, architectural patterns, legal compliance, and security posture, generating prioritized findings and corrective actions.

An audit validates code quality, design-system adherence, legal compliance, architecture conformance, security, and performance. It enforces patterns like strict TypeScript mode, forbidden and required code patterns, and layered architecture rules, then scores and reports on deviations.

Run audits before major releases to ensure readiness, during pull request reviews to catch compliance gaps, or across the full project to establish baseline quality. Audits are designed for pre-release validation and continuous compliance checking.

Yes. The audit workflow scans, analyzes, scores, and reports on architecture conformance, including layered architecture rules and design-system patterns. It identifies violations and recommends corrective actions to align your codebase with defined standards.

Audits produce a structured OPUS AUDIT REPORT containing scores across quality dimensions, prioritized findings with severity levels, and actionable corrective actions. The report supports both high-level summaries and detailed remediation guidance.

Yes. Audit scope includes security and performance evaluation alongside code quality and compliance. It integrates these dimensions into a single comprehensive report with findings and recommendations for each category.