build-fix_skill

Overview

This skill fixes build and TypeScript compilation errors quickly with minimal, targeted code changes. It aims to get the build green without refactoring or architectural changes. The approach is conservative: one fix at a time, verify each change, and stop when the build passes.

How this skill works

It runs the project type checker or build command to collect and categorize errors, then applies focused fixes such as adding type annotations, null checks, and correcting imports. After each change the skill reruns the type check or build to verify no new errors were introduced. The process continues until the build succeeds or no safe minimal fixes remain.

When to use it

• You or CI report "fix the build" or "build is broken"
• TypeScript compilation fails (tsc errors)
• A build command or type checker reports blocking errors
• You want minimal changes rather than refactoring or architecture work
• You need a quick verification loop to get tests or CI passing

Best practices

• Apply one fix at a time and verify by rerunning the type checker or build
• Restrict edits to the minimal lines required to resolve the error
• Avoid refactoring, performance changes, or architectural modifications during the fix
• Add short comments for non-obvious fixes so future reviewers understand intent
• Run unit/integration tests after the build is green to ensure runtime behavior remains correct

Example use cases

• CI failing on TypeScript errors after a dependency upgrade — fix imports and types to restore CI
• Local developer changes cause tsc failures — apply minimal null checks and annotations to unblock work
• Monorepo module resolution errors — correct import paths or export signatures to get the build passing
• Linter or type errors blocking deployment — fix the specific lint/type issue without broader refactors
• Parallelized fixing where multiple agents each handle distinct failing files to reduce turnaround