How do I install the Verification Loop skill?

Run npx skillmds@latest add livelybug/verification-loop-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Verification Loop skill do?

A comprehensive verification system for Claude Code sessions. It is listed under Coding & Dev Tools on SkillMD.

Is Verification Loop safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Verification Loop?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Verification Loop free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Verification Loop?

livelybug (@livelybug) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verification Loop by livelybug — Agent Skill

Name: Verification Loop
Author: livelybug

File contents

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

# 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

# TypeScript projects
npx tsc --noEmit 2>&1 | head -30

# Python projects
pyright . 2>&1 | head -30

Report all type errors. Fix critical ones before continuing.

Phase 3: Lint Check

# JavaScript/TypeScript
npm run lint 2>&1 | head -30

# Python
ruff check . 2>&1 | head -30

Phase 4: Test Suite

# 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

# 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

# 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

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

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

Continuous Mode

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

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.

---name: verification-loop-2description: A comprehensive verification system for Claude Code sessions.---# Verification Loop SkillA comprehensive verification system for Claude Code sessions.## When to UseInvoke 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# Check if project buildsnpm run build 2>&1 | tail -20# ORpnpm build 2>&1 | tail -20```If build fails, STOP and fix before continuing.### Phase 2: Type Check```bash# TypeScript projectsnpx tsc --noEmit 2>&1 | head -30# Python projectspyright . 2>&1 | head -30```Report all type errors. Fix critical ones before continuing.### Phase 3: Lint Check```bash# JavaScript/TypeScriptnpm run lint 2>&1 | head -30# Pythonruff check . 2>&1 | head -30```### Phase 4: Test Suite```bash# Run tests with coveragenpm 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 secretsgrep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10# Check for console.loggrep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10```### Phase 6: Diff Review```bash# Show what changedgit diff --statgit diff HEAD~1 --name-only```Review each changed file for:- Unintended changes- Missing error handling- Potential edge cases## Output FormatAfter 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 PRIssues to Fix:1. ...2. ...```## Continuous ModeFor long sessions, run verification every 15 minutes or after major changes:```markdownSet a mental checkpoint:- After completing each function- After finishing a component- Before moving to next taskRun: /verify```## Integration with HooksThis skill complements PostToolUse hooks but provides deeper verification.Hooks catch issues immediately; this skill provides comprehensive review.

Frequently asked questions

Verification Loop