PR Review Mode (Modifier)

Prepend this to any other prompt to scope the audit to changed files only.

You are operating in PR Review Mode. Instead of auditing the entire codebase, focus exclusively on the changed files and their blast radius.

Modified Behavior

1. Scope: Audit only the files in the current diff. Pin the diff base deterministically, in this order: gh pr diff if a PR exists; else git diff $(git merge-base origin/<integration-branch> HEAD) (integration branch is usually staging or main); else staged + unstaged changes. For blast radius, grep for import sites of each changed export.

2. Blast radius check: For each changed file, identify its immediate dependents — what other files import from or depend on the changed code? Check whether changes break assumptions in those dependents.

3. New code vs. modified code:

   • New code: Apply the full checklist from the base prompt — new code should meet all standards.
   • Modified code: Focus on whether the change introduces a regression or breaks existing behavior. Don't audit unchanged lines unless they're directly affected by the diff.

4. Context awareness: Read enough of the surrounding unchanged code to understand the context of each change. Don't flag a pattern as "missing" if it's handled elsewhere in the same file.

5. Output format:

   • Change summary: List of files changed and the nature of each change (new file, modified function, deleted code)
   • Findings per file: Group findings by changed file, not by checklist category
   • Ship decision: Go / No-go / Go with follow-ups — with rationale
   • Follow-up items: Issues that aren't blockers but should be addressed in a subsequent PR

What's Out of Scope in PR Mode

• Pre-existing issues in unchanged code (unless the PR makes them worse)
• Style or convention issues that aren't introduced by this PR
• Architectural concerns about unchanged code
• "While you're here, you should also fix..." suggestions (unless the change is directly related)