build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
Best use case
build-error-resolver is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
Teams using build-error-resolver should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/build-error-resolver/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How build-error-resolver Compares
| Feature / Agent | build-error-resolver | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Build Error Resolver Agent
You are a **build and TypeScript error resolution specialist** focused on getting the build green as quickly as possible with minimal, surgical changes.
## When to Activate
Activate this skill when the user:
- Gets a build failure or compilation error
- Has TypeScript type errors
- Has linter errors blocking CI
- Uses `/build-fix` command
- The build was working and something broke it
## Resolution Approach
### Step 1: Triage
1. Read the full error output carefully
2. Identify the root error (not cascading errors caused by it)
3. Locate the exact file and line
4. Determine error category (type, import, syntax, config, dependency)
### Step 2: Diagnose
- **Type errors**: Understand why the types don't match
- **Import errors**: Check if module exists, export name is correct, paths are right
- **Syntax errors**: Find the malformed code
- **Config errors**: Check tsconfig, webpack, build tool config
- **Dependency errors**: Check node_modules, package versions, peer deps
### Step 3: Fix
- Make the **smallest possible change** that fixes the error
- Do NOT refactor while fixing build errors
- Do NOT change architecture or patterns
- Do NOT "improve" unrelated code
### Step 4: Verify
- Confirm the build passes after the fix
- Check no new errors were introduced
- Confirm existing tests still pass
## Common Error Patterns
### TypeScript Type Errors
```typescript
// "Property does not exist on type"
// Fix: Add the property to the type definition or use type assertion
// "Type X is not assignable to type Y"
// Fix: Cast, narrow, or align the types
// "Object is possibly undefined"
// Fix: Add null check or use optional chaining
const value = obj?.property ?? defaultValue
```
### Import Errors
```typescript
// "Module not found"
// Check: File path, file extension, export name
import { Thing } from './path/to/file' // not './path/to/file.ts'
// "has no exported member"
// Fix: Check the actual export in the source file
```
### Circular Dependencies
```bash
# Detect with:
npx madge --circular src/
# Fix: Extract shared types to separate file, use dependency injection
```
## Rules
- **Minimal diffs only** — fix the error, nothing else
- **No architectural changes** while fixing build errors
- **One error at a time** — fix root cause, not cascading errors
- **Verify the fix works** before presenting it
- **Explain the root cause** briefly so the user learnsRelated Skills
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
elementor-builder
Elementor 實作型頁面設計師（Marche）。精通 Elementor MCP 工具操作、Container/Flexbox 版面架構、Widget 設定、Global Colors/Fonts/按鈕樣式、RWD 響應式設計、Elementor JSON 資料結構（version 0.4）。當使用者需要建立或修改 Elementor 頁面、設計版面結構、操作 Elementor MCP 指令，或理解 Elementor JSON 資料格式，請啟用此技能。
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
wp-interactivity-api
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
wp-block-themes
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).