Verification Loop

affaan-m/ECC/skills/verification-loop

作者 affaan-mef648e01899ba3e8dc6371642deaaf64b4477775MIT275K 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫4 天前更新

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.

AI 產生的概覽

執行六階段程式碼驗證流程,並產出 PASS/FAIL 就緒報告。

功能
引導代理對程式碼工作階段執行六個驗證階段:建置、型別檢查、程式碼檢查、含涵蓋率的測試、針對密鑰與除錯陳述式的安全 grep,以及差異審查。它為每個階段提供具體 shell 指令,並規定固定報告格式,涵蓋建置、型別、檢查、測試、安全與變更檔案。產出是一份驗證報告,包含供 PR 使用的 READY/NOT READY 整體結論與待修正問題清單。
適用情境
適用於完成功能、重構或較大程式碼變更之後,以及建立 PR 之前。也適合必須通過品質閘門時,或長時間工作階段中需要定期檢查的情況。
執行需求
僅為說明文件,不含隨附指令碼。代理需要具備建置、型別檢查、程式碼檢查與測試工具的專案(例如 npm 或 pnpm、tsc 或 pyright、ruff),以及用於差異審查的 git。指令在本機執行,套件工具可能需要網路存取。

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
# 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
set -o pipefail# TypeScript projectsnpx --no-install 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 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:

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.

來源與署名

來源:affaan-m/ECC位於skills/verification-loop提交ef648e0

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架