← Explore all agents

BUILD AND RUNTIME DIAGNOSTICS / Affaan Mustafa

C++ build error resolver

Diagnoses compilation, CMake, linking and template errors through a small-edit, rebuild and test loop.

“C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.”

01 / THE REASONING

Why this made the selection.

  • It distinguishes missing symbols, duplicate definitions, include problems and template deduction failures.
  • Stop conditions include three repeated failures, a growing error count or an architectural change beyond scope.
  • It is the edit-capable counterpart to the C++ reviewer: Write and Edit are declared, and the mission is a minimal fix for a compile, CMake, or link error.
  • It stops after three failed attempts on the same error, when the fix adds more errors, or when the change would be architectural, and it forbids pragma warning suppression without approval.

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/cpp-build-resolver.md (complete definition)
  • LICENSE (applicable redistribution terms)
  • Host custom-agent documentation; repository installation guidance where applicable

Our findings

  • It distinguishes missing symbols, duplicate definitions, include problems and template deduction failures.
  • Stop conditions include three repeated failures, a growing error count or an architectural change beyond scope.
  • Frontmatter tools are Read, Write, Edit, Bash, Grep, and Glob, so this profile is allowed to change files, unlike the C++ reviewer.
  • The workflow is build, read the error, apply one minimal fix, rebuild, then ctest.
  • Stop conditions include the same error after three attempts and any fix that needs an architectural change. Pragma suppression needs approval.
  • The Markdown file is not a registered subagent until a host loads it from a scanned agents directory.

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. Supply the first failing build log, CMake configuration, compiler standard and affected source/header files.

Before you start

  • Claude Code and a supported model
  • The project-specific C++ 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/cpp-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