Claude
Skills
Sign in
Back

double-check

Included with Lifetime
$97 forever

Double check your work by reviewing changes, asking clarifying questions, and verifying correctness before proceeding. Use when the user says "double check", "verify", "sanity check", or wants validation of recent work.

General

What this skill does


# Double Check

Review recent work for correctness, completeness, and alignment with intent.

## Process

1. **Gather context** — review recent changes, related files, and the original intent. Use the `code_context` MCP tool to look up relevant symbols, files, and blast radius of changes or the `git` tool to `get changes`.

2. **Verify correctness** for each changed file:
   - Compiles/parses (run build or lint)
   - Matches intent (compare done vs asked)
   - No obvious bugs (off-by-one, missing error handling, typos, wrong variable names)
   - Tests pass for changed code
   - No loose ends: TODOs, commented-out code, debug prints, placeholders

3. **Clarify** — make a numbered list and ask one at a time, waiting for each answer. Specific and actionable, not vague.

4. **Report** — what's correct, what's broken, what's unclear.

Related in General