Skip to main content
Agent skill

Verification Loop

Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Verification Loop when an AI agent needs a reusable SKILL.md workflow for this job: Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.

When not to use it

Skip Verification Loop when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/verification-loop
# Save SKILL.md to ~/.claude/skills/verification-loop/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/verification-loop/SKILL.md. For a shared project, commit the folder at .claude/skills/verification-loop/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Verification Loop skill for this task: After completing a feature or significant code change. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Verification Loop Skill

A comprehensive verification system for Claude Code sessions.

## When to Use

Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring

## Verification Phases

### Phase 1: Build Verification ```bash set -o pipefail # report the build's exit status, not tail's # Check if project builds npm run build 2>&1 | tail -20 # OR pnpm build 2>&1 | tail -20 ```

If build fails, STOP and fix before continuing.

### Phase 2: Type Check ```bash set -o pipefail # TypeScript projects npx --no-install tsc --noEmit 2>&1 | sed -n '1,30p'

# Python projects pyright . 2>&1 | sed -n '1,30p' ```

Report all type errors. Fix critical ones before continuing.

### Phase 3: Lint Check

Use `sed` to limit displayed output while consuming the whole stream. This keeps a successful linter from failing on SIGPIPE when `pipefail` is enabled. ```bash set -o pipefail # JavaScript/TypeScript npm run lint 2>&1 | sed -n '1,30p'

# Python ruff check . 2>&1 | sed -n '1,30p' ```

### Phase 4: Test Suite ```bash set -o pipefail # Run tests with coverage npm run test -- --coverage 2>&1 | tail -50

# Check coverage threshold # Target: 80% minimum ```

Report: - Total tests: X - Passed: X - Failed: X - Coverage: X%

### Phase 5: Security Scan ```bash # Check for secrets grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10 grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10

# Check for console.log grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10 ```

### Phase 6: Diff Review ```bash # Show what changed git diff --stat git diff HEAD~1 --name-only ```

Review each changed file for: - Unintended changes - Missing error handling - Potential edge cases

## Target Acceptance

When the requested outcome requires deployment or target-environment verification, report target acceptance separately from local checks. Record the environment and installed version when known, the evidence, and the next permitted check or precise access dependency. Passing local checks, review, merge, or release does not establish target acceptance. Report VERIFIED or FAILED for an executed target check, with its evidence. Do not access production or make external changes without authorization. For local-only tasks, mark target acceptance as not applicable.

For example: local checks PASS; staging verification NOT PERFORMED (no access); next step: an authorized maintainer runs the staging smoke test.

## Output Format

After running all phases, produce a verification report:

``` VERIFICATION REPORT ==================

Build: [PASS/FAIL] Types: [PASS/FAIL] (X errors) Lint: [PASS/FAIL] (X warnings) Tests: [PASS/FAIL] (X/Y passed, Z% coverage) Security: [PASS/FAIL] (X issues) Diff: [X files changed]

Overall: [READY/NOT READY] for PR Target: [VERIFIED/FAILED/NOT PERFORMED/NOT APPLICABLE] (environment/version, evidence) Next permitted step: [check or access dependency; none if complete/not applicable]

Issues to Fix: 1. ... 2. ... ```

## Continuous Mode

For long sessions, run verification every 15 minutes or after major changes:

```markdown Set a mental checkpoint: - After completing each function - After finishing a component - Before moving to next task

Run: /verify ```

## Integration with Hooks

This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.

Intended uses

  • After completing a feature or significant code change
  • Before creating a PR
  • When you want to ensure quality gates pass
  • After refactoring

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.