code-review-mastery

Structure a pull request review by checking security based on OWASP standards, evaluating logic, enforcing SOLID clean code principles, and tracking code metrics before approving. This methodology ensures potential bugs and security flaws are caught before merging.

Provide constructive code review feedback using established interaction patterns that focus on evidence and verification gates. This ensures developers receive actionable input on clean code and security without premature declarations of task completion.

Enforce evidence-based completion claims by applying verification gates that require deterministic task execution proof. This prevents premature success declarations by ensuring reviewers validate security checks, logic, and metrics before a pull request is merged.

No, this code review methodology requires no specific framework dependencies to function. It provides a standalone structured framework covering OWASP security, SOLID clean code principles, and feedback patterns applicable across any development workflow.

Apply SOLID principles and OWASP security checks during the initial pull request review phase. Prioritizing security and logic first ensures maintainability issues and vulnerabilities are identified early in the development lifecycle before verification gates.

Verification gates are needed before declaring a code review complete to enforce evidence-based validation of security, clean code metrics, and logic. This prevents premature success declarations and ensures deterministic task execution across the development workflow.