Menü
Claude Code 会话的全面验证系统。
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | verification-loop |
| description | Claude Code 会话的全面验证系统。 |
| origin | ECC |
一个全面的 Claude Code 会话验证系统。
在以下情况下调用此技能：
# Check if project builds
npm run build 2>&1 | tail -20
# OR
pnpm build 2>&1 | tail -20
如果构建失败，请停止并在继续之前修复。
# TypeScript projects
npx tsc --noEmit 2>&1 | head -30
# Python projects
pyright . 2>&1 | head -30
报告所有类型错误。在继续之前修复关键错误。
# JavaScript/TypeScript
npm run lint 2>&1 | head -30
# Python
ruff check . 2>&1 | head -30
# Run tests with coverage
npm run test -- --coverage 2>&1 | tail -50
# Check coverage threshold
# Target: 80% minimum
报告：
# 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
# Show what changed
git diff --stat
git diff HEAD~1 --name-only
审查每个更改的文件，检查：
运行所有阶段后，生成验证报告：
验证报告
==================
构建: [通过/失败]
类型: [通过/失败] (X 处错误)
代码检查: [通过/失败] (X 条警告)
测试: [通过/失败] (X/Y 通过，覆盖率 Z%)
安全: [通过/失败] (X 个问题)
差异: [X 个文件被修改]
总体: [就绪/未就绪] 提交 PR
待修复问题:
1. ...
2. ...
对于长时间会话，每 15 分钟或在重大更改后运行验证：
设置一个心理检查点：
- 完成每个函数后
- 完成一个组件后
- 在移动到下一个任务之前
运行: /verify
此技能补充 PostToolUse 钩子，但提供更深入的验证。 钩子会立即捕获问题；此技能提供全面的审查。