architect-reviewer · qdhenry — Claude Code subagent: what it does
architect-reviewer — a Claude subagent that reads a change for architectural fit: patterns, SOLID, dependency direction. Useful after structural edits or a new service.
no license ★ 1,357 updated 2026-03-01
.claude/agents/architect-review.mdWhat architect-reviewer does
This subagent reviews a diff the way an architect would: where service boundaries sit, which way dependencies point, whether the change follows patterns the repo already uses. Handy after a module moves, a new service appears, or an API contract shifts and the layering has drifted.
It carries a role definition, a set of design principles (SOLID, DDD, coupling analysis) and a five-step routine: work out why the change exists, find the boundaries it crosses, compare against existing conventions, judge the effect on modularity, then write recommendations. Output has a fixed shape: an impact rating of High, Medium or Low, a compliance checklist, violations tied to file locations and principles, refactoring suggestions.
Tool access is reading and search only: Read, Grep, Glob, LS, plus WebFetch, WebSearch and Task. There are no edit tools, so the agent reports rather than patches. Some entries belong to the sequential-thinking and context7 MCP servers, and those calls need the servers connected in the project first. The model field is set to haiku.
What it helps with
- check that a new service keeps layer boundaries intact
- spot circular references between modules after a merge
- catch SOLID violations in a pending pull request
- work out what an API contract change costs neighbouring components
- map component coupling after a large refactor
Example prompts for the agent
- Run
architect-reviewerover the latest commit and check service boundaries and dependency direction - Review the
billingmodule for SOLID violations and circular imports, and point to the exact lines - Do an architecture pass on this branch before I merge it
How to install architect-reviewer
Manually: put the files in place
.claude/agents/architect-review.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/architect-review.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/architect-review.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about architect-reviewer
How do I install architect-reviewer in Claude Code?
Put the agent file at .claude/agents/architect-review.md inside your project. It holds the role, the tool list and the haiku model setting.
What does architect-reviewer do?
It reads a change against the architectural patterns and SOLID principles already in the codebase, looks for circular dependencies, and estimates the effect on modularity. The result is a structured review with impact rating and refactoring steps.
Does it fix the code it reviews?
No. Its tool list has no editing entries, so it describes the problem and suggests a fix while you make the change.
Similar subagents
All subagents for Code review and refactoring →architect-reviewer by other authors comes first.