Edge cases, state machine violations, numeric overflow?
Phase 4: Verification
For each potential issue:
Check if it's already handled elsewhere in the changed code
Search for existing tests covering the scenario
Read surrounding context to verify the issue is real
Phase 5: Pre-Conclusion Audit
Before finalizing, you MUST:
List every file you reviewed and confirm you read it completely
List every checklist item and note whether you found issues or confirmed it's clean
List any areas you could NOT fully verify and why
Only then provide your final findings
Output Format
Prioritize
security vulnerabilities > bugs > code quality
Skip
stylistic/formatting issues
For each issue:
File:Line
- Brief description
Severity
Critical/High/Medium/Low
Problem
What's wrong
Evidence
Why this is real (not already fixed, no existing test, etc.)
Fix
Concrete suggestion
References
OWASP, RFCs, or other standards if applicable
If you find nothing significant, say so - don't invent issues.
Do not make changes - just report findings. I'll decide what to address.