role-code-review

Structure a code review using a checklist covering functionality, code quality, security, testing, performance, and maintainability. Apply severity levels to issues to communicate recommendations clearly and reduce software defects.

Provide actionable feedback on pull requests by applying a severity-based guidance system. This approach categorizes issues by impact and generates a formal review report that communicates clear recommendations to developers.

Yes, you can use a code review checklist for pre-commit self-checks. The same systematic methodology applies to pre-commit self-reviews, pull requests, and long-form security audits to ensure consistent quality assurance.

Severity-based feedback improves a software quality audit by prioritizing identified issues. It categorizes defects by impact level, enabling reviewers to communicate critical security and performance problems clearly before minor maintainability issues.

A systematic code review process should include a comprehensive checklist, severity-based feedback, and a formal report format. Assess functionality, code quality, security, testing, performance, and maintainability to ensure repeatable quality assurance.