Claude Code Consulting · Subagents · Hooks · Gate Batteries
Subagents · Hooks · Auto-approvals · Wired into a real gate battery
The advisory work concerns repository instructions, scoped hooks and verification around Claude Code. The tool can edit files and run commands; project-specific controls still need explicit configuration, testing and human review.
CLAUDE.md files document repository conventions. Hooks can connect tool actions to project checks, but their presence is not proof of universal enforcement. Inspect the effective configuration and results for the revision being released rather than relying on a fixed gate count.
All three shapes deliver named artifacts — CLAUDE.md files, hook scripts, gate scripts, ADRs. No vendor-doc rehashing.
The referenced repository records describe the method. They do not establish independent validation, client outcomes or universal release compliance.
Related pages explain the approach and its scope.
The umbrella page: what agentic AI means in this practice, the gate catalog, the ADR trail, the release-telemetry endpoint.
Codex as a delivery tool alongside Claude Code. Choice heuristics from real use, not benchmarks.
Research and applied documents that anchor the verification-first method this page relies on.
Bring your CLAUDE.md (if any), your current hook scripts, and the one thing Claude Code is currently getting wrong. A 60-minute call is enough to scope the next step.