code-review

Review a pull request by analyzing diffs, commits, and code paths to surface correctness and integration risk. Apply structured review mechanics to prioritize scope, verify evidence against tests, and generate actionable findings with suggested mitigations.

Analyzing a code diff for safety issues involves verifying findings against code paths, tests, and observable behavior. You load the diff context to identify scope, apply risk assessment, and document actionable findings aligned with your architecture.

Yes, diff analysis supports rollback planning by documenting findings with context and suggested mitigations. It evaluates code changes against your testing strategy and architecture to ensure safe integration and provides actionable rollback guidance.

Code review works with commits, individual diffs, and pull requests. It applies the same evidence-driven analysis across all review scenarios, using code paths and observable behavior to verify findings, prioritize scope, and surface design issues.

Software-design principles are required as the source of truth for code verification to ensure findings align with your architecture. Loading them provides the necessary context to evaluate code changes, verify evidence, and assess integration risk accurately.

Avoid automated code review when you lack diff context, tests, or observable behavior to verify findings. Without these inputs and the software-design source of truth, the analysis cannot accurately prioritize scope, assess risk, or generate actionable mitigations.