sherlock-review

Automate structured code reviews to empirically verify claims using Git and npm tests.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/CENKSSS/valocase-backend --skill sherlock-review-cenksss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sherlock-review
Source: https://github.com/CENKSSS/valocase-backend/tree/main/.claude/skills/sherlock-review
Command: npx skills add https://github.com/CENKSSS/valocase-backend --skill sherlock-review-cenksss

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates evidence-based code reviews, verifying claims made in code implementations through deductive reasoning.

Core Features & Use Cases

  • Evidence Collection: Automates gathering of code, tests, and behavior history.
  • Deductive Analysis: Compares evidence against claims for logical consistency.
  • Documentation: Outputs detailed reports with findings and recommendations.

Quick Start

Conduct a Sherlock review for the PR with ID 123 using the sherlock-review skill.

Frequently Asked Questions about sherlock-review

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

FAQPage Schema
How do I automate evidence-based code review for PR validation?▼

Automate evidence-based code review by using Git and npm test commands to collect code history and test results, comparing them against implementation claims through deductive reasoning to generate a Markdown verification report.

What is deductive analysis in root cause analysis for software bugs?▼

Deductive analysis in root cause analysis is a structured process that compares gathered code, tests, and behavior history against stated claims to verify logical consistency and identify the true source of a bug.

How do I verify claims in code implementations during a bug investigation?▼

Verify claims in code implementations during a bug investigation by automating evidence collection of Git history and npm test results, then applying deductive reasoning to check for logical consistency against the original claims.

Can I use npm test and Git history for feature validation?▼

Yes, you can use npm test commands and Git history for feature validation by gathering empirical evidence of code behavior and comparing it against the feature's expected implementation claims to produce a detailed Markdown report.

What is the best way to document findings from an investigative code review?▼

The best way to document findings from an investigative code review is to output a detailed Markdown report that captures the collected Git and npm test evidence, deductive analysis, and recommendations for truth verification.

Do I need specific dependencies to run a Sherlock review?▼

You do not need specific dependencies to run a Sherlock review; the process utilizes standard Git and npm test commands within your existing environment to gather evidence and validate code claims.