code-review

Automate code review by running parallel review lanes that check source code changes for security vulnerabilities, quality issues, and maintainability concerns. This process evaluates function size, complexity, nesting depth, and performance to provide severity ratings and final merge recommendations.

The best way to check pull requests for hardcoded secrets and injection risks is using a comprehensive code review process. It identifies security vulnerabilities like XSS and CSRF while evaluating code quality, error handling, and duplication to ensure changes meet required standards.

Yes, automated code review works for evaluating function size and code complexity. It analyzes nesting depth, performance impacts, naming conventions, and coupling, providing severity ratings for identified issues to ensure maintainability before merging major feature implementations.

Run a comprehensive code quality assurance check by applying a two-lane review process with code-reviewer and architect agents. This synthesizes security checks, best practices, and maintainability metrics into a final recommendation to validate major code changes.

Yes, you can use parallel review lanes for general code quality assurance. This approach utilizes separate code-reviewer and architect agents to validate source code changes, combining their outputs to deliver a synthesized final recommendation for your codebase.