code-review-standards

To standardize code reviews for security and quality, apply a comprehensive framework of checklists covering vulnerabilities, complexity, performance, and documentation. This ensures consistent feedback and maintainable code across all pull requests.

A security code review checklist should include checks to detect vulnerabilities and enforce safe coding habits. It guides reviewers to identify high-risk findings, prioritize feedback, and attach recommended fixes directly within pull request comments.

Create actionable code review templates by defining prompts and standards for reviewer feedback. These templates guide reviewers to generate consistent, actionable comments that prioritize high-risk findings and suggest specific fixes across all PRs.

Yes, code review standards accelerate engineer onboarding by providing references and examples that train new engineers. They learn security checks, quality patterns, and testing expectations through standardized, battle-tested review documentation.

The best way to enforce code quality and testing expectations is to apply standardized quality gates covering SOLID principles, complexity, naming, and performance. This prevents regressions and improves reliability during the pull request review process.

Formal frontmatter in SKILL.md requires a defined name and description to properly structure code review standards. This formal structure supports references and reviewer templates, ensuring consistent guidance for actionable feedback and team-wide adoption.