← Explore all 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.

“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.”

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.

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 ↗
  1. Read the pinned definition and MIT licence; review the host permissions before use.
  2. Inspect the complete upstream context, place the agent in .claude/agents/ and limit edits/commands to a disposable checkout and the failing target.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. 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

  2. https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/LICENSE

    Supports: Licence and attribution requirements

  3. https://code.claude.com/docs/en/sub-agents.md

    Supports: Host setup and permission defaults

Evidence & Ask