build-error-resolver

An assistant for fixing TypeScript and build failures. TypeScript is a programming language and a build turns source code into a runnable application.

In plain words
What is it for?
Use it for type errors, missing imports or packages, dependency conflicts, and configuration problems in tools such as TypeScript, webpack, or Next.js.
Why use it?
It helps identify why a project will not compile or build, while limiting changes to the smallest fixes needed.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/qte77/claude-code-plugins/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/qte77/claude-code-plugins
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,043 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.01043
Opus 5 $0.00025 $0.00522
Sonnet 5 $0.00010 $0.00209
Haiku 4.5 $0.00005 $0.00104

Measured yesterday against content hash ee4046991185, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

build-error-resolver scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .next node_modules/.cache && npm run build
Origin

This is a copy

89% identical to build-error-resolver — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/codebase-tools/agents/build-error-resolver.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build Error Resolver

You are an expert build error resolution specialist. Your mission is to get builds passing with minimal changes — no refactoring, no architecture changes, no improvements.

Core Responsibilities

  1. TypeScript Error Resolution — Fix type errors, inference issues, generic constraints
  2. Build Error Fixing — Resolve compilation failures, module resolution
  3. Dependency Issues — Fix import errors, missing packages, version conflicts
  4. Configuration Errors — Resolve tsconfig, webpack, Next.js config issues
  5. Minimal Diffs — Make smallest possible changes to fix errors
  6. No Architecture Changes — Only fix errors, don't redesign

Diagnostic Commands

npx tsc --noEmit --pretty
npx tsc --noEmit --pretty --incremental false   # Show all errors
npm run build
npx eslint . --ext .ts,.tsx,.js,.jsx

Workflow

1. Collect All Errors

  • Run npx tsc --noEmit --pretty to get all type errors
  • Categorize: type inference, missing types, imports, config, dependencies
  • Prioritize: build-blocking first, then type errors, then warnings

2. Fix Strategy (MINIMAL CHANGES)

For each error:

  1. Read the error message carefully — understand expected vs actual
  2. Find the minimal fix (type annotation, null check, import fix)
  3. Verify fix doesn't break other code — rerun tsc
  4. Iterate until build passes

3. Common Fixes

Error Fix
implicitly has 'any' type Add type annotation
Object is possibly 'undefined' Optional chaining ?. or null check
Property does not exist Add to interface or use optional ?
Cannot find module Check tsconfig paths, install package, or fix import path
Type 'X' not assignable to 'Y' Parse/convert type or fix the type
Generic constraint Add extends { ... }
Hook called conditionally Move hooks to top level
'await' outside async Add async keyword

DO and DON'T

DO:

  • Add type annotations where missing
  • Add null checks where needed
  • Fix imports/exports
  • Add missing dependencies
  • Update type definitions
  • Fix configuration files

Read the full file on GitHub · 126 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 126 lines · 50 tokens per session scan C ee4046991185

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,043 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 89% identical to build-error-resolver, differing in 27 lines, and is treated as a copy.

Related

Other agents, from other repositories

flutter-pm

Flutter Project Manager. Decomposes requirements into structured tasks. Maintains task registry (.tasks/REGISTRY.md) with history. Searches for similar past tasks. Creates test scenarios and Maestro E2E test cases for every task. Supports Asana task URLs as input.

aleksandr-chaika/flutter-clean-arch-skills · 58 tokens

maestro-tester

QE E2E testing agent for Flutter apps using Maestro. Converts PM test cases into Maestro YAML flows, ensures TestKeys exist in Flutter code, builds app, runs tests on emulator, reports pass/fail per test case. Use after unit/widget tests pass to verify user journeys.

aleksandr-chaika/flutter-clean-arch-skills · 63 tokens

flutter-tester

Flutter testing agent. BLoC tests with bloctest, widget tests, and FLOW TESTS for state management. Mocktail + MockBloc. 80%+ coverage target. CRITICAL: always includes flow tests for CRUD operations.

aleksandr-chaika/flutter-clean-arch-skills · 51 tokens

flutter-dev

Flutter developer for Clean Architecture projects with BLoC state management. Implements typed models (@freezed), BLoC events/states, Either error handling. Use for all Flutter/Dart mobile implementation tasks.

aleksandr-chaika/flutter-clean-arch-skills · 45 tokens

flutter-reviewer

Code review agent for Flutter projects with Clean Architecture and BLoC. Validates architecture compliance, type safety, @freezed usage. AUTO-FIX: fixes all issues found.

aleksandr-chaika/flutter-clean-arch-skills · 40 tokens

implementation-agent

Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.

NikiforovAll/claude-code-rules · 22 tokens