harness-claude

Expert code-review specialist. MUST BE USED immediately after writing or modifying code, before merge. Reviews quality, correctness, and maintainability. Read-only — reports findings with severity, does not edit.

Implementation-planning specialist. Use PROACTIVELY for non-trivial features, refactors, or anything spanning multiple files. Turns a spec into a phased, risk-assessed task plan. Read-only — produces a plan, does not edit code.

System-design specialist. Use PROACTIVELY for architectural decisions, new subsystems, interface/data-model design, or significant refactors. Produces a design note / ADR with trade-offs. Read-only — designs, does not implement.

Security vulnerability specialist. MUST BE USED for any change touching auth, user input, DB queries, file I/O, external calls, crypto, secrets, or payments — and before merging such code. Scans for OWASP Top-10 and secret leakage. Read-only — reports, does not edit.

Test-driven development specialist. Use PROACTIVELY when implementing a feature or fixing a bug. Enforces tests-first (RED → GREEN → REFACTOR) and ≥80% coverage. May write tests and implementation.

Execute a plan via test-driven development — write tests first, then minimal code, phase by phase. Use after /plan (and /architect if needed) to write the actual feature. Delegates to the harness-claude:tdd-guide agent.

Make and record an architecture/design decision for non-trivial work — new subsystems, interfaces, data models, or significant refactors. Use when /plan flags a load-bearing decision. Delegates to the harness-claude:architect agent.

Measure whether a harness component (a skill, agent, or rule) actually earns its keep — run the same task k times with and without it, in isolated git worktrees, and report pass@k (works once) and pass^k (works consistently). Opt-in; not wired into the default pipeline. Use to decide keep-vs-cut on evidence, or to fill the R5 benchmark for a /extract proposal.

Resolve build failures and type/compile errors fast, with minimal diffs. Use when a build or typecheck fails during implementation. Delegates to the harness-claude:build-error-resolver agent.

Release step that closes the loop after /ship — drive a change out to a running environment using the PROJECT'S OWN deploy mechanism (detect, never prescribe a stack), then smoke-test the deployed artifact and keep a guarded rollback path. Deploy is more outward-facing than git push, so it is arm-to-fire — plan and pre-check, then HALT and require an explicit `arm deploy` before any real outward action. Opt-in; invoked explicitly. Use after /ship to push a verified change to staging/prod under the harness's boundary discipline.

15 hooks across 5 events