Find Bugs

Review changes on this branch for bugs, security vulnerabilities, and code quality issues.

When to Use

• You need a review focused on bugs, security issues, or risky code changes.
• The task involves auditing the current branch diff rather than implementing new behavior.
• You want a structured review process with checklist-driven verification against changed files.

Phase 1: Complete Input Gathering

1. Establish the requested base and head as verified commit SHAs. Check the remote/default branch if needed; do not assume a stale local branch is current. Read the full branch diff with git diff "$BASE_SHA...$HEAD_SHA" --, using validated refs in separately quoted arguments. Include staged and unstaged changes when they are in scope; preserve the checkout.
2. If output is truncated, read each changed file individually until you have seen every changed line
3. List all files modified in this branch before proceeding

Phase 2: Attack Surface Mapping

For each changed file, identify and list: