---
name: double-check
description: Audit just-completed implementation or refactor work before claiming it is done or closing its issue. Use when acceptance, specification match, tests, migrations, or loose ends must be checked; do not trigger for read-only exploration or early progress reports.
---

# Double-check your work

Audit completion against evidence, not confidence.

## Read First

Discover and follow the target repository's guidance for review thresholds, testing, code and documentation style, generated files, migrations, and issue completion. Read the original request, acceptance criteria, and any governing specification or design.

## Procedure

1. Identify the owned diff, explicit requirements, acceptance criteria, and protected unrelated work while the patch is still uncommitted.
2. Map every requirement to concrete evidence from the final files, focused tests, native parsers or linters, generated-artifact checks, and migration or compatibility checks where applicable.
3. Search for likely loose ends: stale names and paths, old representations, duplicate implementations, bypass paths, temporary probes, unhandled lifecycle states, and documentation that still describes the prior behavior.
4. If the user authorized implementation or repair, fix in-scope failures, rerun affected checks, and inspect the resulting complete diff. Otherwise report findings without mutation.
5. Apply the repository's review threshold. Request independent review when the change is broad, cross-boundary, security-sensitive, destructive, or otherwise requires authority beyond self-review.
6. Do not claim completion while any requirement lacks evidence. Distinguish an unrelated baseline failure from an unverified requirement; neither is silently converted into success.

## Reporting

Report one line per requirement or applicable review area: pass with concrete evidence, or fail with what remains. Cite anchors such as file paths, command output, issue criteria, or specification sections; do not report only that the work “looks good.”

If a failure is outside the owned slice, name it as unrelated and leave the protected files alone.
