Repository navigation
feat: Claude harness — parallel review team + dev workflow - #4
Merged
Merged
Conversation
Adds a .claude/ configuration with:
- 6 agents (architect, security, performance, style, synth, implementer),
all pinned to opus
- 7 skills — 2 orchestrators (code-review, code-development) plus 5
domain skills, each with its own references/ for Go + pgx + indexer
checklists
- Finding-synthesis skill with a shared markdown finding schema and a
strict severity ladder so the four parallel reviewers produce merge-
able output
- Fan-out / fan-in pattern: the four reviewers run in parallel, each
writes _workspace/{category}_findings.md, synthesizer merges into
_workspace/report.md
- CLAUDE.md at repo root describing the harness, trigger rules,
directory layout, and when NOT to use it
Triggers the harness for requests like 'review this', 'audit this PR',
'implement X and review it', etc. Simple questions bypass the harness
and are answered directly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
.claude/configuration to the repo that wires up a 6-agent teamfor code review and code development. On any review or implementation
request, four reviewers (architecture, security, performance, style)
run in parallel and a synthesizer merges their findings into one
prioritised report.
What's in the harness
Agents (all
model: opus):architect-reviewer— module boundaries, dependency direction, concurrency ownership, transaction disciplinesecurity-auditor— SQL injection (pgx), secret leakage, authz, input validation, TLS/crypto, container hardeningperformance-analyst— hot-path allocations, goroutine leaks, pgx pool sizing, CopyFrom vs. loop-insert, retry amplification, indexer-specific concerns (batch sizing, AIMD tuning, dead-letter amplification, range fragmentation)style-reviewer— Go idioms, naming, comments, project conventions inferred from existing codereport-synthesizer— lead; dedupes, re-ranks by severity, writes the consolidated reportimplementer— writes new code for the dev workflow (used only bycode-development)Skills:
code-review— main review orchestrator (fan-out + synth)code-development— dev orchestrator (implement → review the diff)architecture-review,security-audit,performance-analysis,style-review— per-reviewer methodology + a dedicated reference doc with Go/pgx/Docker checklists calibrated to this codebasefinding-synthesis— shared finding schema, strict severity ladder, merge rulesPattern: fan-out / fan-in.
_workspace/{category}_findings.md_workspace/report.md_workspace_prev_{timestamp}/Key design choices
criticalis reserved for exploit / data loss / outage on the live path. The severity guide in.claude/skills/finding-synthesis/references/severity-guide.mdis the single source of truth that both reviewers and the synth apply.Directory layout
Test plan
code-reviewskill triggers, four reviewers fan out, synth produces a report