alinafe82 Diff Interrogation
Force a diff to prove its behavior, test coverage, and risk profile before acceptance.
Scope
Use for the task in the description. For example: Review this retry diff for duplicate payment side effects. Do not activate for: Reformat these comments without changing behavior.
Workflow
- Summarize the behavior change, not the file list.
- Identify the highest-risk lines or decisions.
- Check for missing tests, widened permissions, silent failures, data loss, and hidden coupling.
- Ask explanation questions for unclear changes.
- Recommend commit, revise, or reject.
Evidence
Diff or PR summary. Test output if available. Relevant files, issue, expected behavior, and security-sensitive areas. Report the outcome with relevant behavior change, highest-risk lines, missing proof, questions. Adapt the format to the task; omit empty fields. Never claim checks ran without observed results.
Boundaries
Do not paste secrets, tokens, customer records, private incident details, or proprietary code into public summaries. Use line references and redacted snippets. Continue authorized read-only and reversible local work through the requested outcome. If evidence is missing, inspect available sources before asking; report limits honestly.
References
For worked examples, open simple or edge case only when useful. Routing cases record positive and negative activation examples for review; they are not a model benchmark.