build-error-resolver

A coding-agent role focused on fixing build failures and TypeScript errors. TypeScript is JavaScript with checks that catch many mistakes before the program runs.

In plain words
What is it for?
Use it to diagnose and fix type errors, compilation failures, missing imports, dependency problems, and configuration errors with small changes.
Why use it?
It gets a project building again while limiting changes to the errors, avoiding refactoring or redesign.

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/sjarmak/coding-agent-workflows/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/sjarmak/coding-agent-workflows
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 910 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin 98% 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.00910
Opus 5 $0.00025 $0.00455
Sonnet 5 $0.00010 $0.00182
Haiku 4.5 $0.00005 $0.00091

Measured 2d ago against content hash 60b9032f6d34, 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 2d ago.

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

98% identical to build-error-resolver — 24 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.

source/agents/build-error-resolver.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 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 · 115 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. 2d ago First seen · 115 lines · 50 tokens per session scan C 60b9032f6d34

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 910 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 98% identical to build-error-resolver, differing in 24 lines, and is treated as a copy.

Related

Other agents, from other repositories

test-engineer

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

addyosmani/agent-skills · 35 tokens

model-add-remove

模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.

modelstudioai/cli · 0 tokens

frontend-design

React 前端技术设计专家。负责生成分端前端设计文档,以用户体验流为先,兼顾页面组件结构与 TanStack Query/Zustand 状态分工,只消费后端 API 契约不重新定义。.

timzaak/web-dev-skills · 54 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

audit-agent

Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.

marconae/speq-skill · 42 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens