code-auditor · gupsammy — Claude Code subagent: what it does, how to install
code-auditor goes over the code you just changed, flags logic bugs, vague names and leftovers, then says in plain words what needs fixing.
no license ★ 276 updated 2026-10-29
/plugin marketplace add gupsammy/Claudest
/plugin install claude-coding@ClaudestWhat code-auditor does
code-auditor is a subagent for Claude aimed at code quality after a change: logic, clarity, naming, unused branches. It runs on sonnet with Read, Grep, Glob and Bash, and keeps project memory, so the conventions it picks up in your repo survive into the next run.
There are two modes. A quick question — is this function name any good, should this error be caught here — gets a short advisory answer whose first line is Mode: Advisor, with no report attached. Ask for a quality review, or let it fire after a diff, and the auditor takes over: it lists the files it read, gives a verdict, then works through error paths, boundary cases, nesting and stray debug lines. Dead-code hunts walk the import graph and label each hit as confirmed or as a candidate a human should look at.
Bash is read-only on purpose: git diff, git log, tree, find -type f, wc -l. Build and test commands are out of reach, so a fault that only appears at runtime will not turn up here. Security, speed and architecture sit outside the brief as well; it names the matching agent in one sentence and moves on.
What it helps with
- review only the files a refactor touched
- find exports that nothing imports
- match new code to the project's naming and error-handling habits
- get a straight answer on one name or one
catchblock - strip leftover debug prints and stale TODOs
Example prompts for the agent
- Run code-auditor over the files from my last commit and tell me what to fix.
- Ask code-auditor if
parseInvoiceis the right name for this helper. - Have code-auditor hunt for dead exports under
src/billing.
How to install code-auditor
1Plugin marketplace
/plugin marketplace add gupsammy/Claudest/plugin install claude-coding@Claudest2Manually: put the files in place
.claude/agents/code-auditor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/code-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/code-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 code-auditor
How do I install code-auditor in Claude Code?
Add the marketplace with /plugin marketplace add gupsammy/Claudest, then install the plugin: /plugin install claude-coding@Claudest.
What does code-auditor do?
It reviews changed code for logic mistakes, weak names, drift from project conventions and pieces nobody uses. As an advisor it answers one narrow question; as an auditor it returns a report on the files it inspected.
How is it different from security-auditor?
Vulnerabilities belong to security-auditor, bottlenecks to performance-auditor, module layout to architecture-auditor. code-auditor stays on code quality and only points at the right agent when something falls outside that.
Similar subagents
All subagents for Code review and refactoring →code-auditor by other authors comes first.