Claude Code 验证循环技能 - 代码质量自动检查与测试工具，提升开发效率

verification-loop by affaan-m/everything-claude-code

1,100 周安装量

102,100 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/affaan-m/everything-claude-code --skill verification-loop

开发开发运维监控

🇨🇳中文介绍

验证循环技能

一个适用于 Claude Code 会话的全面验证系统。

使用时机

在以下情况调用此技能：

完成一个功能或重大代码变更后
创建 PR 之前
当您希望确保质量关卡通过时
重构之后

验证阶段

阶段 1：构建验证

# 检查项目是否能构建
npm run build 2>&1 | tail -20
# 或者
pnpm build 2>&1 | tail -20

如果构建失败，停止并在继续之前修复问题。

阶段 2：类型检查

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

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

报告所有类型错误。在继续之前修复关键错误。

阶段 3：代码规范检查

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

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

阶段 4：测试套件

# 运行测试并生成覆盖率报告
npm run test -- --coverage 2>&1 | tail -50

# 检查覆盖率阈值
# 目标：最低 80%

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

阶段 5：安全扫描

# 检查密钥
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

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

阶段 6：差异审查

# 显示变更内容
git diff --stat
git diff HEAD~1 --name-only

审查每个变更文件，检查：

非预期的变更
缺失的错误处理
潜在的边界情况

运行所有阶段后，生成验证报告：

验证报告
==================

构建：     [通过/失败]
类型：     [通过/失败] (X 个错误)
规范：      [通过/失败] (X 个警告)
测试：     [通过/失败] (X/Y 通过，Z% 覆盖率)
安全：      [通过/失败] (X 个问题)
差异：      [X 个文件已变更]

总体：     [已就绪/未就绪] 可提交 PR

待修复问题：
1. ...
2. ...

对于长时间会话，每 15 分钟或在重大变更后运行验证：

设置心理检查点：
- 完成每个函数后
- 完成一个组件后
- 开始下一个任务前

运行：/verify

此技能是对 PostToolUse 钩子的补充，但提供更深入的验证。钩子能立即捕获问题；此技能提供全面审查。

🇺🇸English

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.

Weekly Installs

614

Repository

affaan-m/everyt…ude-code

GitHub Stars

72.1K

First Seen

Feb 12, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykFail

Installed on

codex541

opencode527

gemini-cli511

github-copilot502

cursor481

kimi-cli477