← Explore all agents

BUILD AND RUNTIME DIAGNOSTICS / Affaan Mustafa

Dart/Flutter build error resolver

Diagnoses analyzer, platform build, package-resolution and generated-code failures with bounded changes.

“Dart/Flutter build, analysis, and dependency error resolution specialist. Fixes `dart analyze` errors, Flutter compilation failures, pub dependency conflicts, and build_runner issues with minimal, surgical changes. Use when Dart/Flutter builds fail.”

01 / THE REASONING

Why this made the selection.

  • The workflow separates null/type errors from pub solver conflicts, build_runner output and Android/iOS configuration.
  • It stops when package upgrades change behaviour or competing platform constraints need a decision.
  • It fixes Dart and Flutter analyze, pub, and build_runner failures with minimal edits, and it forbids dynamic and // ignore: as ways to silence a type error.
  • It stops when platform constraints conflict and need a user decision, instead of picking an Android or iOS setting on its own.

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

Our findings

  • The workflow separates null/type errors from pub solver conflicts, build_runner output and Android/iOS configuration.
  • It stops when package upgrades change behaviour or competing platform constraints need a decision.
  • Tools are Read, Write, Edit, Bash, Grep, and Glob.
  • Principles forbid // ignore: without approval and dynamic as a type silencer, and they prefer null-safe patterns over bang operators.
  • Stop conditions include three repeats, a fix that adds errors, behavior-changing package upgrades, and conflicting platform constraints.
  • The file does not place itself in ~/.claude/agents/. The host docs tie availability to that location.

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 target platform, Dart/Flutter toolchain, pubspec files, generator configuration and full failure output.

Before you start

  • Claude Code and a supported model
  • The project-specific Dart/Flutter 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/dart-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