code-verifierlisted

# Code Verifier ## Purpose Runs the full quality gate for a project: lint, type-check, tests, and import validation. Provides a structured, parseable result that the orchestrator uses to decide whether to proceed or trigger a fix loop. **Distinct from `task-implementer` Phase 5:** task-implementer does inline self-verification during implementation. `code-verifier` is an independent gate that runs after all tasks in a wave are complete — giving a clean, consolidated view of the whole diff, not per-task. **Input:** Codebase path + worktree path + scope (changed files or full project) **Output:** `VERIFICATION_RESULT` structured report — gate status (pass/fail), per-check results, actionable findings ## When to Use - Dispatched by `job-orchestrator` after each task-implementer wave (mandatory) - Dispatched by `job-orchestrator` after each fix iteration - Run standalone: "verify my code", "run quality gate", "/code-verifier" - Any time you need a reproducible, structured view of project health ## Architecture: 4 Phases ``` Phase 1: DETECT → Auto-detect stack, tooling, commands Phase 2: RUN → Execute lint → type-check → tests → import-check Phase 3: ANALYZE → Parse outputs, classify findings by severity Phase 4: REPORT → Emit VERIFICATION_RESULT ``` --- ## Workflow ``` Code Verifier Progress: - [ ] Phase 1: Detect stack and tooling - [ ] Phase 2: Run verification checks - [ ] Phase 3: Analyze and classify findings - [ ] Phase 4: Report results ``` --- #