Harness Review

Review for concrete defects and risks. Reviews are read-only by default: identify actionable findings without changing files, commits, branches, pull requests, or external state.

Review Procedure

1. Establish the requested scope and applicable repository rules.

2. Inspect the complete relevant diff and enough surrounding code, tests, configuration, or documentation to understand behavior.

3. Verify each suspected issue. Trace inputs, control flow, affected callers, and existing tests instead of relying on pattern matching alone.

4. Classify actionable findings with references/review-severity.md.

5. Keep line ranges tight and ensure the cited line is part of, or directly explains, the defect.

6. Optionally validate structured findings before rendering them:

   python3 scripts/validate_review.py findings.json
   

7. Present findings in priority order. If none remain after verification, state that no actionable findings were found and mention any material verification gap.