sherlock-review

Evidence-based code review examines the claimed fix against diffs, tests, logs, and historical changes to confirm the root cause was identified and addressed. Compare the fix to observed behavior in tests and reproduction steps to ensure the claim matches reproducible proof.

Gather evidence by collecting diffs, test results, runtime logs, and change history. Eliminate impossible explanations systematically, then document findings rooted in reproducible proof that connects claims to observed results.

Yes. Investigative review applies to performance claims by gathering evidence from benchmarks, logs, and behavioral changes, then comparing claimed improvements against measured results to confirm the fix is valid.

Root your conclusions in gathered evidence: diffs showing what changed, tests demonstrating the fix works, and logs confirming behavior. Structure findings to eliminate impossible explanations and make the proof reproducible for others.

Use deduction when claims about bug fixes, features, or root causes don't align with observed behavior. Gather code, test, and historical evidence to form conclusions by eliminating impossible explanations and confirming what the evidence shows.

Yes. The skill integrates code-review, security, and performance perspectives to investigate claims across all three domains, using evidence from diffs, tests, and behavior to verify fixes and root causes.