← ClaudeAtlas

doublechecklisted

Deep verification that all changes meet requirements and preserve correctness
lacerbi/dotclaude · ★ 2 · AI & Automation · score 74
Install: claude install-skill lacerbi/dotclaude
## Context - Branch and files: !`git status --short --branch` - Unstaged changes: !`git diff` - Staged changes: !`git diff --cached` The injected diffs cover working-tree changes. If relevant work was committed during this conversation, inspect the corresponding commit or branch diff too. Focus on work from this conversation unless otherwise specified; unrelated changes may belong to the user or another agent. ## Your Task Perform a meticulous verification and comprehensive review of all work done. **Depending on the size and complexity of the verification, deploy one or more specialized sub-agents** to handle different aspects, split as appropriate for the task. Choose sub-agents appropriate for task complexity (see `CLAUDE.md` for agent selection guidance—verification tasks typically need Opus, maybe Sonnet for routine verifications, never Haiku). Establish the actual change scope before reviewing. Treat verification as read-only unless the user explicitly asks for fixes. Verify that: - All changes align with the original goals and requirements - Modifications preserve file integrity and correctness - Nothing is missing or requires additional updates - Changes work coherently together ### Deeper Review Go beyond surface-level correctness. Evaluate the work for: - **Completeness**: Are all requirements addressed? Are there gaps, missing scenarios, or implicit expectations left unhandled? - **Correctness**: Does the logic hold? Are there subtle errors, flawed assump