verify

Reviews uncommitted git diffs line by line and runs tests before committing.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill verify-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/cursor/.claude/skills/verify
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill verify-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often declare work done based on confidence rather than evidence, shipping diffs with drift, dead code, untested paths, and unrun test suites. This Skill enforces a skeptical self-review of your own uncommitted changes so 'done' is earned through actual verification. ## Core Features & Use Cases - Frozen review scope: Captures an immutable base SHA, validates refs, and refuses empty scopes so the review target never shifts mid-pass. - Spec traceability: Locates the originating spec from changed paths, commit messages, or feature ledgers, and checks the diff traces 1:1 to the original request and success criteria. - Line-by-line diff audit: Reads every changed line for logic errors, edge cases, dead code, over-engineering, and missing tests, callers, or error handling. - Real execution: Runs format, lint, and the full test suite plus the actual user flow, then fixes findings and re-reviews the fixes. - Use Case: After implementing a feature slice, run /verify to catch an unused import, a missing caller update, and a failing edge-case test before handing off to independent review or committing. ## Quick Start Ask the assistant to run /verify on your current uncommitted changes to review the diff and execute the full test suite before committing.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I review my own code changes before committing in git?▼

Run /verify to freeze a base SHA with git rev-parse, then read every changed line from git diff against that base. It checks drift from the request, edge cases, dead code, and missing tests, then runs your lint and test commands before you commit.

How to verify a diff matches the original feature request?▼

The pass re-reads the original request and contract scenarios, then traces the diff 1:1 to success criteria. It locates the originating spec from changed docs/specs paths, commit messages, or the active features.json ledger, and flags unrequested additions for removal.

What is the difference between self-review and independent code review?▼

Self-review with /verify is the implementer checking its own uncommitted diff before claiming completion. Independent review (judge) happens afterward by a separate reviewer; /verify complements rather than replaces it and stays single-model.

Can I verify changes against a specific branch instead of HEAD?▼

Yes, pass a base ref such as your default branch and the skill computes the merge-base with HEAD as the frozen review base. Invalid refs are rejected immediately, and the captured SHA stays immutable for the entire pass.

What happens when there are no changes to verify?▼

The preflight lists tracked changes via git diff and untracked files via git ls-files. If both lists are empty, the skill stops immediately with the exact message 'Nothing to verify.'