You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo ships a small team of specialized Claude Code subagents in `.claude/agents/`. They are **stateless reviewers**: each runs in its own context, is handed a specific deliverable, and returns its findings to the main session — they do not talk to each other. **The main session is the integrator.** You drive them; you do not delegate the whole task and walk away.
4
+
5
+
**Invoke an agent by name** for the matching job — e.g. *"review this with the fortran-physics-reviewer"* or *"run the regression-guardian against develop"*. Do **not** "consult all the agents" reflexively: that burns the token budget and produces noise. Pick the agent whose job matches the change.
6
+
7
+
## Roster
8
+
9
+
| Agent | Model | Role — invoke when… |
10
+
|---|---|---|
11
+
|`fortran-physics-reviewer`| opus | A physics kernel, numerical method, derivative, integral, or quadrature was written/changed. Audits fidelity to the reference papers and the Fortran GPEC source. Carries project memory (correspondence map + per-domain audit checklists for KineticForces and InnerLayer), so its reviews compound — let it record findings. |
12
+
|`clean-code-reviewer`| opus | A logical chunk of code is ready and you want readability/maintainability review for a fusion physicist audience (naming, magic numbers, docstrings, structure). |
13
+
|`julia-performance-optimizer`| opus | A specific function/hotspot is slow or perf-sensitive (type stability, allocations, hot-loop work in ODE/kinetic/resistive-layer paths). |
14
+
|`fast-interpolations-optimizer`| opus | Code uses FastInterpolations.jl and you want allocation-free / optimal-search-type review. |
15
+
|`regression-guardian`| sonnet |**Before merging any substantive change** (mandatory per the Regression Harness policy — see `docs/development/regression-harness.md`), or when you need to know whether a tracked numerical quantity moved. Runs the harness, reports the table, flags non-OK rows, proposes new cases. |
16
+
17
+
## Recommended review pipeline for a substantive change
18
+
19
+
Run sequentially, reading each agent's findings before launching the next:
20
+
21
+
1.**`fortran-physics-reviewer`** — physics fidelity first; a fast-but-wrong result is worthless.
22
+
2.**`clean-code-reviewer`** — readability and maintainability.
23
+
3.**`julia-performance-optimizer`** and/or **`fast-interpolations-optimizer`** — only if the change is performance-relevant.
24
+
4.**`regression-guardian`** — always, last, before merge. Confirms the numbers didn't silently move.
25
+
26
+
Not every change needs all four. A docs-only change needs none; a pure perf refactor still needs the physics reviewer (to confirm no numerical change) and the regression-guardian.
27
+
28
+
## Budget
29
+
30
+
Every consultation is bounded — see **Subagent Consultations** in `/CLAUDE.md` (≤30 tool uses, ≤10 min, one concrete deliverable, never re-launch a runaway). The agent bodies now self-enforce this, but state the budget in your prompt anyway and always hand the agent the specific file paths to act on.
0 commit comments