build-fix

Fix build and TypeScript errors with minimal changes

11 stars

Best use case

build-fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Fix build and TypeScript errors with minimal changes

Teams using build-fix 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

$curl -o ~/.claude/skills/build-fix/SKILL.md --create-dirs "https://raw.githubusercontent.com/MeroZemory/oh-my-droid/main/skills/build-fix/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/build-fix/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How build-fix Compares

Feature / Agentbuild-fixStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Fix build and TypeScript errors with minimal changes

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 Fix Skill

Fix build and TypeScript errors quickly with minimal code changes. Get the build green without refactoring.

## When to Use

This skill activates when:
- User says "fix the build", "build is broken"
- TypeScript compilation fails
- `npm run build` or `tsc` reports errors
- User requests "minimal fixes" for errors

## What It Does

Delegates to the `build-fixer` agent (Sonnet model) to:

1. **Collect Errors**
   - Run `npx tsc --noEmit` to get all TypeScript errors
   - Or run `npm run build` to get build failures
   - Categorize errors by type and severity

2. **Fix Strategically**
   - Add type annotations where missing
   - Add null checks where needed
   - Fix import/export statements
   - Resolve module resolution issues
   - Fix linter errors blocking build

3. **Minimal Diff Strategy**
   - NO refactoring of unrelated code
   - NO architectural changes
   - NO performance optimizations
   - ONLY what's needed to make build pass

4. **Verify**
   - Run `npx tsc --noEmit` after each fix
   - Ensure no new errors introduced
   - Stop when build passes

## Agent Delegation

```
Task(
  subagent_type="oh-my-droid:build-fixer",
  model="claude-sonnet-4-5-20250929",
  prompt="BUILD FIX TASK

Fix all build and TypeScript errors with minimal changes.

Requirements:
- Run tsc/build to collect errors
- Fix errors one at a time
- Verify each fix doesn't introduce new errors
- NO refactoring, NO architectural changes
- Stop when build passes

Output: Build error resolution report with:
- List of errors fixed
- Lines changed per fix
- Final build status"
)
```

## Stop Conditions

The build-fixer agent stops when:
- `npx tsc --noEmit` exits with code 0
- `npm run build` completes successfully
- No new errors introduced

## Output Format

```
BUILD FIX REPORT
================

Errors Fixed: 12
Files Modified: 8
Lines Changed: 47

Fixes Applied:
1. src/utils/validation.ts:15 - Added return type annotation
2. src/components/Header.tsx:42 - Added null check for props.user
3. src/api/client.ts:89 - Fixed import path for axios
...

Final Build Status: ✓ PASSING
Verification: npx tsc --noEmit (exit code 0)
```

## Best Practices

- **One fix at a time** - Easier to verify and debug
- **Minimal changes** - Don't refactor while fixing
- **Document why** - Comment non-obvious fixes
- **Test after** - Ensure tests still pass

## Use with Other Skills

Combine with other skills for comprehensive fixing:

**With Ultrawork:**
```
/ultrawork fix all build errors
```
Spawns multiple build-fixer agents in parallel for different files.

**With Ralph:**
```
/ralph fix the build
```
Keeps trying until build passes, even if it takes multiple iterations.

**With Pipeline:**
```
/pipeline debug "build is failing"
```
Uses: explore → architect → build-fixer workflow.

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.