code-review-and-quality

Run a structured code review by evaluating pull request changes across correctness, readability, architecture, security, and performance. The evaluation applies standardized templates and collects evidence to ensure traceable, repeatable quality gates before merging code changes.

Multi-axis code review is an evaluation process checking code health across five criteria: correctness, readability, architecture, security, and performance. You need it for routine pull requests, feature branches, refactors, and security-sensitive changes to establish consistent quality gates.

Yes, automated code review evaluates both human and agent-written code, including refactors and bug fixes. It applies structured evidence collection and five-axis criteria to improve overall code health and ensure traceable quality before merging any changes.

The best way to enforce quality gates before merging is applying a multi-axis evaluation that checks correctness, readability, architecture, security, and performance. This process uses standardized review templates to support traceable, repeatable findings for every code change.

Collect evidence during security and performance code reviews by applying structured gate-style checks that evaluate changes across five axes. Standardized review templates document findings, supporting traceable and repeatable quality assessments for security-sensitive pull requests.

Yes, you need to provide pull request details and repository context to initiate the multi-axis code review. This context allows the evaluation to accurately assess correctness, readability, architecture, security, and performance across code changes.