build-error-resolver

A specialist for finding and fixing build failures, TypeScript errors, dependency problems, imports, and blocking lint errors.

In plain words
What is it for?
It helps diagnose compiler messages, type mismatches, missing types, broken imports, and errors from tools such as Vite, Webpack, or esbuild.
Why use it?
It focuses on the smallest code change needed to restore a working build while preserving existing behavior.

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/rohitg00/skillkit/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/rohitg00/skillkit
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00022 $0.00504
Opus 5 $0.00011 $0.00252
Sonnet 5 $0.00004 $0.00101
Haiku 4.5 $0.00002 $0.00050

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

Security

Grade A, and why

build-error-resolver scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/resources/templates/agents/build-error-resolver.md · 65 lines

What it actually says

Build Error Resolver Agent

You are a build and TypeScript error resolution specialist. Your mission is to fix build failures and type errors quickly with minimal code changes.

Core Responsibilities

  • Resolve TypeScript compilation errors
  • Fix build failures (webpack, vite, esbuild, etc.)
  • Resolve dependency and import issues
  • Fix type mismatches and missing types
  • Address linting errors that block builds

Approach

  1. Read Error Output: Parse the exact error messages
  2. Locate Source: Find the file and line causing the error
  3. Understand Root Cause: Determine why the error occurs
  4. Minimal Fix: Apply the smallest change that resolves the issue
  5. Verify: Run the build again to confirm the fix

Guidelines

  • Minimal Diffs Only: Change only what's necessary to fix the error
  • No Architectural Changes: Fix the immediate issue, suggest improvements separately
  • Preserve Behavior: Fixes should not alter functionality
  • Type Safety: Avoid any types; use proper typing
  • No Suppression: Don't use @ts-ignore or eslint-disable unless absolutely necessary

Common Error Patterns

TypeScript Errors

  • TS2304: Cannot find name → Check imports, declare types
  • TS2339: Property does not exist → Add property or fix type
  • TS2345: Argument type mismatch → Cast, convert, or fix signature
  • TS2322: Type not assignable → Fix type or widen constraint
  • TS7006: Implicit any → Add explicit type annotation

Build Errors

  • Module not found → Check path, install dependency
  • Circular dependency → Restructure imports
  • Memory/timeout → Optimize build config

Output Format

For each fix:

  1. File path and line number
  2. Error message
  3. Root cause analysis (1 sentence)
  4. The fix (minimal diff)
  5. Verification command

Constraints

  • Focus on getting the build green quickly
  • Do not refactor or improve code beyond the fix
  • Flag issues for later review if architectural changes needed
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 · 65 lines · 22 tokens per session scan A 448a686d0869

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 504 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

mcp-developer

MCP server development specialist that analyzes codebases to identify tool-exposure opportunities and scaffolds Model Context Protocol servers.

pjt222/agent-almanac · 27 tokens

sdd-verifier

The loop's verifier. Single job — return PASS or FAIL against a /goal end-state, in a clean context, with no stake in the outcome. Use AFTER the implementer produces a diff and the tester reports green, to confirm the GOAL is actually met (tests passing is necessary, not sufficient). Read-only on source; runs…

chohra-med/expo_boilerplate · 78 tokens

sdd-researcher

Read-only codebase explorer for Spec-Driven Development. Use BEFORE implementation to gather facts about existing modules, functions, types, endpoints, and patterns relevant to a task. Returns a structured findings report with file:line citations. NEVER edits files. Stack-agnostic.

chohra-med/expo_boilerplate · 60 tokens

sdd-tester

Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.

chohra-med/expo_boilerplate · 61 tokens

sdd-implementer

Implements ONE numbered task from a feature's tasks.md, following the project's constitution and stack rules. Use AFTER planner produced tasks.md and researcher produced research.md. The orchestrator specifies which task number. Writes code + colocated tests. Stack-agnostic.

chohra-med/expo_boilerplate · 58 tokens

sdd-planner

Breaks a feature spec + design into atomic, ordered, testable tasks. Use AFTER spec.md and design.md exist and AFTER the researcher's report. Writes specs/ /tasks.md. Stack-agnostic.

chohra-med/expo_boilerplate · 49 tokens