Build Fix

What it does

The Build Fix skill automatically resolves build and compilation errors in your codebase with minimal changes, aiming to get your project building successfully without significant refactoring. It utilizes a specialized agent ("build-fixer") powered by the Sonnet model to collect errors, strategically apply fixes (like adding type annotations or null checks), and verify each change doesn't introduce new issues. The focus is strictly on resolving build failures – no architectural changes or performance optimizations are performed.

When to use it

• When you hear "fix the build" or "build is broken."
• TypeScript compilation fails.
• Your project’s build command or type checker reports errors.
• You need minimal fixes for errors and want to avoid extensive refactoring.

Key capabilities

• Error Collection: Runs type check (e.g., tsc --noEmit, mypy) or build commands to identify errors.
• Strategic Fixing: Adds missing type annotations, null checks, corrects import/export statements, resolves module resolution issues, and fixes linter errors blocking the build.
• Minimal Diff Strategy: Limits changes to only what's necessary for a passing build; avoids refactoring unrelated code or architectural changes.
• Verification: Runs type check commands after each fix to ensure no new errors are introduced.
• Agent Delegation: Uses the "oh-my-claudecode:build-fixer" agent with the Sonnet model, following specific instructions for error resolution.

Example prompts

• “fix the build”
• “build is broken”
• “TypeScript compilation failed - can you fix it?”

Tips & gotchas

• The skill focuses solely on resolving build errors; it won't address broader code quality issues or performance optimizations.
• It prioritizes minimal changes, so complex refactoring will not be performed.
• Consider combining with other skills like Ultrawork (for parallel fixing), Ralph (for persistent attempts), or Pipeline (for a debugging workflow).