design-implementation-reviewer

To verify code correctness and find logic errors, perform a three-layer critical review: inspect code quality, trace end-to-end execution flow, and validate goal achievement. This surfaces defects like edge cases and failure paths that the original design may have missed.

The best way to conduct a deep code review for root cause analysis is to apply bug-finding with skepticism, validating whether the implementation works with real data. Structure findings by severity, providing root cause identification and fix guidance for each detected defect.

To check if your code achieves expected end-to-end behavior, perform goal achievement verification alongside execution flow tracing. This validates that the implementation functions correctly with real data, rather than just superficially matching design specifications.

No, this code review approach explicitly excludes security vulnerability scanning. It focuses entirely on correctness validation, requirements verification, and detecting logic errors to ensure the implementation achieves expected end-to-end goals.

To create test plans for critical bugs found during requirements verification, generate dedicated test cases specifically for critical and high severity issues. Structure these test plans alongside the root cause analysis and fix recommendations for each finding.