feat: enforce fixing all issues regardless of authorship

Adds a mandatory "No Pre-Existing Issue Exceptions" policy to prevent
Claude from dismissing errors, warnings, or linting failures it didn't
write. Also extends the code-reviewer agent with an Issue Ownership
Policy requiring concrete fixes rather than passive reporting.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-25 20:56:30 -05:00
parent a32828facd
commit 16dc81e66d
2 changed files with 38 additions and 0 deletions

View File

@@ -170,6 +170,16 @@ grep -rn "\`.*SELECT" src/ --include="*.ts"
[Explanation of why this matters]
```
## Issue Ownership Policy
When you find any issue during review — regardless of whether it was introduced by the current PR — you must:
1. Flag it in the review output with file and line reference
2. Provide a concrete fix, not just a description of the problem
3. **Never** write "pre-existing" or "out of scope" as a reason to skip fixing something
If an issue is too large to fix within the current review scope, escalate it explicitly to the user with a clear explanation of what is needed. Do not silently drop it.
## Special Considerations
### For Python Code