Runs multi-phase code verification: build, type checks (TypeScript/Python), linting, tests with 80% coverage goal, security scans for secrets/console.log, git diff review. Use after features, refactors, before PRs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/everything-claude-code:verification-loopThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
一个用于 Claude Code 会话的全面验证系统。
一个用于 Claude Code 会话的全面验证系统。
在以下场景调用此技能(Skill):
# 检查项目是否可以构建
npm run build 2>&1 | tail -20
# 或者
pnpm build 2>&1 | tail -20
如果构建失败,请停止并修复后再继续。
# TypeScript 项目
npx tsc --noEmit 2>&1 | head -30
# Python 项目
pyright . 2>&1 | head -30
报告所有类型错误。在继续之前修复关键错误。
# JavaScript/TypeScript
npm run lint 2>&1 | head -30
# Python
ruff check . 2>&1 | head -30
# 运行带有覆盖率报告的测试
npm run test -- --coverage 2>&1 | tail -50
# 检查覆盖率阈值
# 目标:最低 80%
报告内容:
# 检查密钥
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
# 显示变更内容
git diff --stat
git diff HEAD~1 --name-only
审查每个变更的文件,确认:
运行完所有阶段后,生成一份验证报告:
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. ...
对于长时间的会话(Session),每 15 分钟或在重大变更后运行一次验证:
设置心理检查点:
- 完成每个函数后
- 完成一个组件后
- 在开始下一个任务之前
运行:/verify
此技能(Skill)是对 PostToolUse 钩子(Hooks)的补充,但提供了更深层次的验证。
钩子可以立即发现问题;此技能则提供全面的审查。
npx claudepluginhub codelably/harmony-claude-codeRuns multi-stage verification on code changes: build, type checks (tsc/pyright), lint (eslint/ruff), tests with coverage, security scans (secrets/console.log), git diff review. Use before PRs, after refactors.
Runs a multi-phase verification pipeline (build, types, lint, tests, security, diff review) after code changes or before PRs.
Runs a multi-phase verification loop including build, type check, lint, tests, security scan, and diff review. Useful before creating a PR or after significant changes.