adityaarakeri Self Review
Read the actual change as a skeptical maintainer, not from memory.
Select the Mode
- Author mode: Review work produced within the current approved implementation. Fix in-scope findings, rerun affected checks, and review the resulting diff again.
- Review-only mode: Report findings and evidence without modifying files, formatting, snapshots, dependencies, git state, or external systems. Implement fixes only when separately requested.
Review Process
- Inspect repository instructions, status, the complete diff, untracked files, and the original request. Preserve unrelated work.
- Trace each changed input through callers, state transitions, outputs, and failure paths. Check empty, boundary, large, Unicode, concurrent, retry, and partial-failure cases where relevant.
- Follow changed trust boundaries beyond literal changed lines. Inspect authorization, secrets, injection, filesystem and process execution, unsafe rendering, deserialization, dependency risk, and data exposure.
- Check errors and cleanup: failures must surface; resources, transactions, locks, and temporary files must be released.
- Check scope and consistency: no debug leftovers, dead code, accidental generated files, unsupported API changes, or unrelated formatting churn.
- Check tests: new behavior has meaningful coverage, assertions can fail, and boundary behavior is exercised.
- Validate each potential finding against callers, guards, tests, and framework guarantees. Omit speculation.
Report
Lead with independently actionable findings ordered by severity, each with a precise location, trigger, impact, evidence, and remediation direction. Then list material assumptions and verification gaps. If no finding survives validation, say so explicitly.