---
title: "Rust build error resolver: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/ecc-rust-build-resolver/
description: "Resolves Rust compilation, ownership, trait and Cargo-feature errors with a minimal-change verification loop."
---

# Rust build error resolver: review, role & definition · Undominated.ai

> Resolves Rust compilation, ownership, trait and Cargo-feature errors with a minimal-change verification loop.

[← Explore all agents](/agents/)

BUILD AND RUNTIME DIAGNOSTICS / Affaan Mustafa

# Rust build error resolver

Resolves Rust compilation, ownership, trait and Cargo-feature errors with a minimal-change verification loop.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/rust-build-resolver.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Affaan Mustafa
 Licence [MIT ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/LICENSE)
 Revision b92f181b3b74
 [Read what was—and wasn’t—checked ↓](#review)

“Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.”

 [Affaan Mustafa · upstream description ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/rust-build-resolver.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It inspects duplicate dependencies and enabled features, preferring a targeted package update to a full lockfile refresh.
- The rules prohibit using unsafe or unwrap solely to silence the compiler and stop when a data-ownership redesign exceeds scope.
- It fixes cargo check, clippy, and borrow-checker errors with minimal edits, and it forbids unsafe, unwrap, and #[allow(unused)] as shortcuts.
- It stops when a borrow error needs an ownership redesign, which keeps a green build from becoming a silent model change.

### A good fit for

 - Provide the failing crate/workspace, full compiler error, feature selection and minimum supported Rust version.
- Receive source-linked repairs and build/clippy/test status, or a stop when ownership design must change.
- A Rust compile error that should be fixed and rechecked with cargo check and cargo test.
- Refusing an unsafe or unwrap silence when the compiler is reporting a lifetime or borrow error.

### Weigh up before choosing

 - Cloning, RefCell, added lifetime bounds and edition changes are contextual proposals, not interchangeable compiler fixes. Preserve API semantics and MSRV.
- Cargo checks/builds can execute build scripts and write outputs; tests and dependency updates require a controlled project environment.
- The definition references separate upstream support material (rust-patterns); it is not packaged here.
- The source selects the sonnet model alias; confirm it exists in the configured host.
- Source-only listing: inspect the upstream context and referenced dependencies before adapting this definition.
- cargo audit runs only when the binary exists. The file does not install it, and it does not claim a missing auditor is a clean bill.
- Write, Edit, and Bash are declared, so the profile can change the crate and run cargo. It does not publish the crate.
- rust-patterns is referenced and not included.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - agents/rust-build-resolver.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable

### Our findings

 - It inspects duplicate dependencies and enabled features, preferring a targeted package update to a full lockfile refresh.
- The rules prohibit using unsafe or unwrap solely to silence the compiler and stop when a data-ownership redesign exceeds scope.
- The diagnostic order is cargo check, clippy denying warnings, fmt --check, cargo tree --duplicates, and cargo audit if installed.
- Principles say never use unsafe to dodge the borrow checker and never add unwrap to silence a type error.
- A stop condition is a borrow-checker error that requires redesigning the ownership model, after at most three attempts at the same error.
- Registration is not part of the file. The host says the subagent is available because the Markdown lives in ~/.claude/agents/.

### Not established by this review

 - No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md)
 - Read the pinned definition and MIT licence; review the host permissions before use.
- Inspect the complete upstream context, place the agent in .claude/agents/ and limit edits/commands to a disposable checkout and the failing target.
- Provide the failing crate/workspace, full compiler error, feature selection and minimum supported Rust version.

### Before you start

 - Claude Code and a supported model
- The project-specific Rust toolchain, dependencies and a reproducible failure

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated repository and tool access

 - Declared tools: Read, Write, Edit, Bash, Grep, Glob. The host enforces tool access; shell execution can modify files or contact services.

### Cost model

The definition is reusable under its stated licence. Host/model usage, execution environments and connected services can incur separate charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Complete upstream definition at reviewed commit ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/rust-build-resolver.md) Checked 2026-10-14 https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/rust-build-resolver.md Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
- [Applicable upstream redistribution licence ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/LICENSE) Checked 2026-10-14 https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/LICENSE Supports: Licence and attribution requirements
- [Host custom-agent configuration ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host setup and permission defaults

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### C++ build error resolver ↗ Diagnoses compilation, CMake, linking and template errors through a small-edit, rebuild and test loop.](/agents/ecc-cpp-build-resolver/)[### Dart/Flutter build error resolver ↗ Diagnoses analyzer, platform build, package-resolution and generated-code failures with bounded changes.](/agents/ecc-dart-build-resolver/)[### Go build error resolver ↗ Resolves Go compiler, module, vet and linter failures while keeping changes bounded to the reported build problem.](/agents/ecc-go-build-resolver/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
