arcanea-code-review

Code reviews should systematically evaluate security, logic, architecture, maintainability, testing, and performance using a structured checklist. This Skill provides a prioritized framework—Critical, Important, Suggestions, Nitpicks—to guide thorough reviews during pull requests without losing focus on what matters most.

Focus on functional requirements: security and input validation, error handling, readability, adherence to project patterns, DRY and SOLID principles, test coverage, and documentation. Constructive feedback on these areas lifts the entire team's code quality and shared understanding.

Separate feedback into four priority levels: Critical (blocking issues), Important (significant concerns), Suggestions (improvements), and Nitpicks (minor style points). This prioritization helps reviewers and authors focus on architectural and functional impact while deferring stylistic debates.

Yes. Code reviews are an effective enforcement mechanism for security checks, input validation, error handling, and adherence to maintainability principles like DRY and SOLID. Consistent application during pull requests and CI checks codifies team standards.

Structure feedback to be clear, actionable, and respectful. Ground comments in specific concerns—security vulnerabilities, logic errors, architectural misalignment, test gaps—rather than subjective preferences, so authors understand the rationale and can respond confidently.