architecture-auditor · gupsammy — Claude Code subagent: setup and use
architecture-auditor reviews system structure, detects circular dependencies, and suggests design patterns when features touch multiple modules.
no license ★ 276 updated 2026-10-29
/plugin marketplace add gupsammy/Claudest
/plugin install claude-coding@ClaudestWhat architecture-auditor does
The subagent runs in two distinct roles. As an advisor, it answers mid-implementation questions about patterns and trade-offs, grounding suggestions in the current codebase layout. As an auditor, it inspects directory structures, checks layer separation, and pinpoints issues down to the file and line number.
Inspection relies on Read, Grep, Glob, and read-only Bash calls like tree, find -type f, or wc -l. Mutating operations stay off limits: the agent never commits changes, deletes files, or runs test suites.
Styling details, naming nitpicks, and single-file formatting are intentionally ignored. The subagent focuses entirely on cross-module boundaries, God modules, and structural coupling.
What it helps with
- detect circular dependencies and leaky abstractions across packages
- evaluate architectural trade-offs before introducing a new pattern
- audit layer boundaries after refactoring shared code
- spot oversized modules that break single-responsibility boundaries
Example prompts for the agent
- Which pattern should I use to decouple our payment provider from billing?
- Audit the architecture of the recent changes across our core services
- Check whether these new modules introduce circular imports
How to install architecture-auditor
1Plugin marketplace
/plugin marketplace add gupsammy/Claudest/plugin install claude-coding@Claudest2Manually: put the files in place
.claude/agents/architecture-auditor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/architecture-auditor.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/architecture-auditor.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 architecture-auditor
How to install architecture-auditor in Claude Code?
Add the marketplace source with /plugin marketplace add gupsammy/Claudest, then install it by running /plugin install claude-coding@Claudest.
What is the difference between Advisor and Auditor modes?
Advisor mode provides brief design guidance when planning code changes. Auditor mode inspects files, maps dependencies, and builds a structured issue report categorized by severity.
Does the agent check linter rules or code style?
No, it ignores formatting, naming, and single-file linter warnings. Its checks are strictly confined to module relationships and structural design choices.
Similar subagents
All subagents for Code review and refactoring →architecture-auditor by other authors comes first.