---
title: "Dart/Flutter build error resolver: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/ecc-dart-build-resolver/
description: "Diagnoses analyzer, platform build, package-resolution and generated-code failures with bounded changes."
---

# Dart/Flutter build error resolver: review, role & definition · Undominated.ai

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

[← Explore all agents](/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.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/affaan-m/everything-claude-code/blob/b92f181b3b748d1abbc2afd94af6aa7d8c8fca29/agents/dart-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)

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

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

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.

### A good fit for

 - Provide the target platform, Dart/Flutter toolchain, pubspec files, generator configuration and full failure output.
- Receive error-to-fix explanations, analyzer/test status and unresolved platform or dependency constraints.
- A flutter analyze or pub resolution failure that should be fixed and rechecked with flutter analyze.
- A Gradle or CocoaPods failure where the prompt's stop rule is a conflicting platform constraint.

### Weigh up before choosing

 - Its examples include force unwraps, dependency overrides and deletion of generated outputs; do not apply these without establishing the intended data and generator contract.
- Package upgrades, cache repair, CocoaPods changes and clean commands mutate the environment; execute only the diagnostics needed for the failing target.
- The definition references separate upstream support material (flutter-dart-code-review); 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.
- Commands include flutter, dart, pub, and pod updates through Bash, plus Write and Edit. The file does not install the Flutter SDK.
- It does not include the flutter-dart-code-review skill it cites.
- A suggested version bump in the sample output is an example, not a resolved lockfile from this review.

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 ↗](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 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

### 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/dart-build-resolver.md) Checked 2026-10-14 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
- [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/)[### 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/)[### PyTorch build error resolver ↗ Traces tensor shapes, devices and gradient paths to diagnose a bounded training or inference crash.](/agents/ecc-pytorch-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/)
