code-review-and-quality

You can automate code review for pull requests by running this skill to analyze changes across correctness, readability, architecture, security, and performance before merging. It evaluates code changes against predefined quality standards to catch potential production errors.

A multi-axis code review covers five key dimensions: correctness, readability, architecture, security, and performance. This comprehensive assessment ensures code changes meet quality standards and reduces errors before merging into the main branch.

Yes, you can run a security audit and performance testing before merging by executing this skill on your code changes. It incorporates security and performance checks as part of its five-dimension analysis to ensure code quality.

The best way to ensure code quality before a merge is to run an automated review process that checks for correctness, readability, architecture, security, and performance. This skill enforces predefined quality standards on every pull request.

Architecture analysis during a code review evaluates the structural design of your code changes to ensure they align with predefined quality standards. It is one of five dimensions assessed, alongside correctness, readability, security, and performance, before merging.