evidence-review

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

SKILL.md

GitHub

Evidence Review

  1. Read the requested diff and applicable repository guidance.
  2. Trace each suspected problem to a concrete file, behavior, or broken contract.
  3. Return actionable findings ordered by impact.
  4. Include a precise location, failing scenario, evidence, and fix direction.
  5. Omit style preferences and unsupported speculation.
  6. State explicitly when no actionable finding is verified.