Code Review Workflow

To find bugs in a pull request, review code changes for correctness, regressions, and security risks using a severity-first process. This approach reports issues in descending severity so the most important problems surface immediately instead of being buried.

A findings-first code review workflow evaluates diffs and branches by concentrating on behavior, validation, access control, and test gaps. It prioritizes risk-focused coverage over style nits, ensuring severe correctness issues are explicitly ordered and addressed.

Yes, you can run diff analysis on database and infra changes. The review process applies to backend, frontend, database, CI, docs, infra, and mobile changes, catching regressions and missing tests across these domains.

Review a pull request for missing test coverage by analyzing the diff for behavior and validation gaps. The review identifies missing tests and routes specialized checks to appropriate domains while noting any residual risks.

Yes, the code review workflow handles specialist security deferrals. When a change touches security, database, or frontend domains, it routes those specific checks to the appropriate specialized skill rather than attempting a superficial review.