Evidence-first engineering

Don't just ship code.
Prove it's ready.

A disciplined code-review workflow for Claude Code. Combine independent scrutiny, real verification, safer Git operations, and developer understanding — before approval.

GitHub starsGitHub issuesnpm version
The principle

Evidence, not assumptions.

Passing tests matter, but they don't automatically prove a change is correct, safe, or understood. Make reasoning and evidence part of the review itself.

01 / INSPECT

Understand the repository

Read project guidance, conventions, Git state, tests, build scripts, and existing safeguards before proposing changes.

02 / CHALLENGE

Review independently

Use a clean reviewer context to examine the actual diff, challenge assumptions, and report actionable findings.

03 / VERIFY

Prove the exact change

Run real checks, tie results to the precise change, and disclose what was not tested or cannot be guaranteed.

The workflow

From task brief to informed approval.

A clear sequence that keeps the developer in control and makes review outcomes traceable.

01 · InspectRead instructions and project state.
02 · AgreeDefine scope and acceptance evidence.
03 · ImplementMake the smallest agreed change.
04 · VerifyRun checks and independent review.
05 · UnderstandExplain the diff before approval.
Local hooks can be bypassed or removed. Use server-side branch protection and CI for authoritative enforcement.
Getting started

Available now as a repository skill.

Install the published npm package directly from your project root. The installer adds the skill to your Claude Code skills directory without overwriting an existing installation.

Terminal · planned distribution command
npx verified-code-review

The package is published on npm. By default it installs into .claude/skills/ in the current project; use the --global option for a user-wide installation. Existing skill directories are never overwritten.

Project status

Open development. Honest limitations.

This project is an engineering workflow aid, not a security certification or a guarantee that software is defect-free. Adapt checks to your stack, keep credentials out of logs, and never claim a check ran unless it really did.