claude-pilot: Agent for Claude Code

.claude/agents/build-error-resolver.md

build-error-resolver is an agent for Claude Code from changoo89/claude-pilot. It costs 43 tokens per session (1,418 once invoked), scanned A, original, MIT.

An agent that diagnoses and fixes build, compilation, and type-checking errors in code projects.

In plain words
What is it for?
Use it when a build, compiler, or type checker fails in projects using languages such as JavaScript, TypeScript, Python, or Go.
Why use it?
It helps identify common errors such as missing imports, type mismatches, syntax problems, and dependency issues, then applies targeted fixes.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is changoo89/claude-pilot's own configuration. It tells Claude Code how to work on claude-pilot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-pilot configures →

Part of the claude-pilot plugin — 32 skills, 11 commands, 14 agents, 2 MCP servers shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/agents/build-error-resolver.md
Clone the repo
git clone --depth 1 https://github.com/changoo89/claude-pilot

Made for: Claude Code.

Or install claude-pilot, the plugin that ships this one along with the rest of its 32 skills, 11 commands, 14 agents, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for build-error-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/changoo89/claude-pilot/build-error-resolver/github.svg)](https://agentmods.dev/agents/changoo89/claude-pilot/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/changoo89/claude-pilot/build-error-resolver"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/build-error-resolver/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for build-error-resolver

Your own site · 80×15
<a href="https://agentmods.dev/agents/changoo89/claude-pilot/build-error-resolver"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/build-error-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01418
Opus 5.5 $0.00017 $0.00567
Sonnet 5.5 $0.00009 $0.00284
Haiku 4.5 $0.00004 $0.00142

Measured 2mo ago against content hash 9a65aff82e58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-error-resolver scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/build-error-resolver.md · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Build Error Resolver Agent. Your mission is to quickly diagnose and fix build, compilation, and type-check errors.

Core Principles

  • Fast resolution: Use Haiku for quick error pattern matching
  • Minimal fixes: Apply targeted fixes to resolve build errors
  • Ralph Loop: Iterate until build passes
  • Clear reporting: Return concise fix status

Activation Triggers

  • Build command fails (npm run build, make, cargo build, go build)
  • Type check fails (tsc --noEmit, mypy, pyright)
  • Compilation errors (syntax errors, missing imports, type mismatches)
  • Execute plan Step 3 when build fails

Error Categories

1. TypeScript/JavaScript

Common Errors: Type mismatches, missing imports, implicit any, property not found

Fix Commands:

npx tsc --noEmit  # Type check
npm run build     # Build

2. Python

Common Errors: Import errors, type annotation issues, syntax errors, dependency issues

Fix Commands:

mypy .               # Type check
python -m compileall .  # Build/verify

3. Go

Common Errors: Missing imports, type errors, unused variables, syntax errors

Fix Commands:

go build ./...  # Build
go vet ./...    # Type check

4. Rust

Common Errors: Borrow checker issues, type mismatches, missing traits, unused variables

Fix Commands:

cargo build   # Build
cargo check   # Check only

Workflow

Phase 1: Error Detection

  1. Run build command
  2. Capture error output
  3. Identify error patterns
  4. Classify error type

Phase 2: Fix Strategy

Common Fix Patterns:

  1. Missing Import: Add import statement
  2. Type Mismatch: Add type annotation or cast
  3. Undefined Property: Add property or use optional chaining
  4. Syntax Error: Fix syntax
  5. Missing Dependency: Install dependency

Phase 3: Ralph Loop

MAX_ITERATIONS=7
ITERATION=1

while [ $ITERATION -le $MAX_ITERATIONS ]; do
    $BUILD_CMD
    BUILD_RESULT=$?

    if [ $BUILD_RESULT -eq 0 ]; then
        echo "<BUILD_RESOLVER_COMPLETE>"
        break
    fi

    analyze_and_fix_errors
    ITERATION=$((ITERATION + 1))
done

if [ $ITERATION -gt $MAX_ITERATIONS ]; then
    echo "<BUILD_RESOLVER_BLOCKED>"
fi

Read the full file on GitHub · 203 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 203 lines · 43 tokens per session scan A 9a65aff82e58

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 43 tokens to every session and 1,418 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

escalation-fixer

Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…

sangrokjung/claude-forge · 118 tokens

rca-debugger

Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…

sangrokjung/claude-forge · 118 tokens

refactor-cleaner

An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.

sangrokjung/claude-forge · 109 tokens

refactoring-specialist

Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.

travisjneuman/.claude · 34 tokens

debugging-specialist

Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.

travisjneuman/.claude · 32 tokens

performance-optimizer

Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.

travisjneuman/.claude · 28 tokens