sherlock-review

Conduct evidence-based code reviews using deductive reasoning to validate implementation claims.

2|2|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/summarybotng/summarybot-ng --skill sherlock-review-summarybotng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sherlock-review
Source: https://github.com/summarybotng/summarybot-ng/tree/main/.claude/skills/sherlock-review
Command: npx skills add https://github.com/summarybotng/summarybot-ng --skill sherlock-review-summarybotng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic, evidence-based approach to code review, ensuring that claims about code functionality, fixes, or performance are rigorously validated against actual behavior and data.

Core Features & Use Cases

  • Deductive Reasoning: Applies logical deduction to evidence to determine the truth behind implementation claims.
  • Evidence Gathering: Guides the collection of code, tests, and runtime behavior for thorough analysis.
  • Use Case: When a developer claims a bug fix has been implemented, this Skill helps verify if the fix truly addresses the root cause or merely a symptom, by examining code changes, test results, and reproduction steps.

Quick Start

Use the sherlock-review skill to investigate the claim that PR #123 fixes a memory leak.

Frequently Asked Questions about sherlock-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a bug fix actually addresses the root cause instead of just treating a symptom?

Evidence-based code review validates bug fixes by systematically observing code changes and runtime behavior, then applying deductive reasoning to eliminate impossibilities. This confirms whether the implementation truly resolves the root cause or merely masks the symptom.

What is deductive reasoning in code review and how does it validate implementation claims?

Deductive reasoning in code review validates implementation claims by systematically observing code, tests, and runtime behavior, then eliminating impossibilities to determine the truth. It proves whether stated functionality matches actual observed reality.

How do I perform root cause analysis on a pull request claiming to fix a memory leak?

Performing root cause analysis on a pull request requires gathering code changes, test results, and reproduction steps as evidence. You then apply logical deduction to validate if the fix truly addresses the memory leak's origin rather than suppressing it.

Does evidence-based code review work for validating new feature implementations?

Evidence-based code review works for validating new feature implementations by collecting runtime behavior and test data as proof. It systematically checks observed reality against the developer's implementation claims to confirm the feature functions as described.

What are the limitations of using deductive reasoning for bug verification?

Limitations of using deductive reasoning for bug verification include the absolute necessity of comprehensive evidence gathering. Without accurate runtime behavior data, reproduction steps, and test results, logical deduction cannot reliably eliminate impossibilities or validate root causes.