Ask Agent to review branch changes for bugs, regressions, missing tests and unclear docs.
Name the review target
Tell Agent what to compare and what kind of risk matters.
Review the current branch against main.
Focus on bugs, regressions, security risks, and missing tests.Set the review standard
Ask for findings first, with file and line references.
List findings by severity.
Include file and line references.
Keep summaries after the findings.Ask for verification
Ask Agent to run or recommend checks that match the changed surface.
Run the relevant tests if they are available.
If a check is missing, explain the risk.Turn findings into fixes
After review, ask Agent to fix confirmed issues.
Fix the high-confidence findings only.
Do not refactor unrelated code.
Rerun the checks after the fixes.Next
Fix confirmed findings, or investigate a specific failure before editing.
Related
Use project instructions for branch, test and review rules. Child forks explains isolated review runs.