with one click
Sistema de verificación completo para sesiones de Claude Code.
npx skills add https://github.com/affaan-m/ECC --skill verification-loopCopy and paste this command into Claude Code to install the skill
Menu
Sistema de verificación completo para sesiones de Claude Code.
npx skills add https://github.com/affaan-m/ECC --skill verification-loopCopy and paste this command into Claude Code to install the skill
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 | Sistema de verificación completo para sesiones de Claude Code. |
| origin | ECC |
Sistema de verificación completo para sesiones de Claude Code.
Invocar este skill:
# Verificar si el proyecto compila
npm run build 2>&1 | tail -20
# O
pnpm build 2>&1 | tail -20
Si el build falla, DETENER y corregir antes de continuar.
# Proyectos TypeScript
npx tsc --noEmit 2>&1 | head -30
# Proyectos Python
pyright . 2>&1 | head -30
Reportar todos los errores de tipo. Corregir los críticos antes de continuar.
# JavaScript/TypeScript
npm run lint 2>&1 | head -30
# Python
ruff check . 2>&1 | head -30
# Ejecutar pruebas con cobertura
npm run test -- --coverage 2>&1 | tail -50
# Verificar umbral de cobertura
# Objetivo: mínimo 80%
Reportar:
# Verificar secretos
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
# Verificar console.log
grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10
# Mostrar qué cambió
git diff --stat
git diff HEAD~1 --name-only
Revisar cada archivo modificado en busca de:
Después de ejecutar todas las fases, producir un reporte de verificación:
REPORTE DE VERIFICACIÓN
=======================
Build: [PASS/FAIL]
Tipos: [PASS/FAIL] (X errores)
Lint: [PASS/FAIL] (X advertencias)
Pruebas: [PASS/FAIL] (X/Y pasadas, Z% cobertura)
Seguridad: [PASS/FAIL] (X problemas)
Diff: [X archivos modificados]
General: [LISTO/NO LISTO] para PR
Problemas a Corregir:
1. ...
2. ...
Para sesiones largas, ejecutar la verificación cada 15 minutos o después de cambios importantes:
Establecer un checkpoint mental:
- Después de completar cada función
- Después de terminar un componente
- Antes de pasar a la siguiente tarea
Ejecutar: /verify
Este skill complementa los hooks PostToolUse pero proporciona una verificación más profunda. Los hooks detectan problemas de inmediato; este skill proporciona una revisión completa.