comprehensive-review

This approach integrates architecture, quality, readability, security, and documentation assessments into a single cohesive evaluation. It generates concrete remediation suggestions and documentation improvements suitable for pull requests, refactors, and onboarding workflows.

Yes, a focused analysis can be tailored using the --focus parameter to target architecture, quality, readability, security, or documentation individually. This allows for targeted static analysis without running a full end-to-end review on the codebase.

Yes, this comprehensive review supports TypeScript, Go, Python, Rust, and more. It applies unified code review workflows across multiple languages and project sizes, satisfying requirements for automated static analysis and clean architecture adherence.

By performing a comprehensive review, you can validate adherence to clean architecture and DDD during refactors or PR reviews. It analyzes structural design alongside quality and security to generate concrete remediation suggestions aligning your codebase with architectural standards.

Integrating documentation as one of five core assessment perspectives within a comprehensive review is the best way to automate this. It evaluates documentation alongside static analysis and generates actionable suggestions for documentation improvements.

You should avoid a unified five-perspective review when you only need a quick syntax check or isolated linting pass. For highly targeted tasks, using the --focus parameter is more efficient than generating a full end-to-end architectural and security evaluation.