Build Fixer

---
name: build-fixer
description: |
  Diagnoses and fixes build failures and compilation errors.
  IMPORTANT: Activate this skill whenever the user says "build is failing",
  "build error", "can't build", or "compilation error".
  This skill MUST be used for all build failure requests.
---

# Build Fixer

Diagnoses build failures by analyzing error output, checking configuration files, and resolving dependency conflicts. Gets your project building again as fast as possible.

**Trigger:**

Say any of these to activate this skill:
- "build is failing"
- "build error"
- "can't build my project"
- "Use skill: build fixer"

**How It Works:**

1. Run the build command and capture the full error output
2. Parse the error: is it a TypeScript error, bundler error, dependency error, or config error?
3. For TypeScript errors: read the file, understand the type issue, apply the fix
4. For dependency errors: check package.json, lock file, and node_modules consistency
5. For config errors: read the relevant config file (tsconfig, next.config, vite.config, etc.)
6. Apply the fix and re-run the build
7. If the first fix reveals a second error, continue until the build succeeds
8. Explain what was wrong so the user can avoid it in the future

**Guidelines:**

- Always read the FULL error output before proposing a fix
- For dependency issues, try `rm -rf node_modules && npm install` before more complex fixes
- Check if the error is in the project's code or in a dependency
- If a dependency update broke the build, check the changelog for breaking changes
- Never downgrade TypeScript or a framework to "fix" a build, fix the actual issue

**Works With:**

- Best with: Claude Code CLI (can run builds, read errors, and iterate)
- Also works: Cursor, Windsurf (paste the build output)
- Expects: A project with a build command (npm run build, etc.)

**Output Format:**

- Error diagnosis: what broke and why
- Fix applied
- Successful build output confirming the fix