anorth Anorth review
Read the change set and the surrounding code it depends on. Determine which themes are relevant to the diff. Load one subagent for each theme and hand it the theme file and instructions to review the diff for issues it covers. Subagents should use a cheap model; ask the user if you haven't been told which is appropriate.
Collate the reported issues. Output issues in decreasing order of importance. Suggest how to resolve them. Do not apply substantive edits before discussion.
Always
Naming— identifiersStyle— dead weight, constants, order, localityComments— comments, docs, stale nearby comments
When the diff matches
API Shape— public functions, types, endpoints, events, persisted formatsArchitecture— modules, layers, where state or effects liveChange Scope— mixed features, refactors, or cleanups in one PRConcurrency— shared mutable state, threads/coroutines, timersCoupling— module boundaries, wiring, cross-component APIsDependencies— manifests, lockfiles, vendored or generated code, new librariesCI locally— CI, build, lint, or codegen stepsErrors— new or changed failure paths, error types, panicsInvariants— validation, state transitions, persistence, aggregatesObservability— logs, metrics, journals, or swallowed failuresTests— tests, fixtures, doubles, or test helpers