fix-build

Automate repair of build and TypeScript errors with minimal edits.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/shaun0927/codex-superskills --skill fix-build-shaun0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-build
Source: https://github.com/shaun0927/codex-superskills/tree/main/skills/build-fix
Command: npx skills add https://github.com/shaun0927/codex-superskills --skill fix-build-shaun0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix build and compilation errors quickly with minimal changes, helping you get the build green without large refactors.

Core Features & Use Cases

  • Error collection: runs type checks or builds to identify failures and categorize by type and severity.
  • Strategic fixes: adds missing type annotations, resolves import/export issues, fixes linter blockers, and corrects module resolution with minimal diffs.
  • Verification: re-runs checks after each fix to ensure no new errors and stops when the build passes.

Quick Start

Invoke the build-fix skill to collect and fix build errors automatically until the project builds clean.

Frequently Asked Questions about fix-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix TypeScript build errors automatically without large refactors?

You can resolve TypeScript build errors by applying minimal fixes like adding missing type annotations and correcting import paths. This Skill automates collecting build failures, applying strategic minimal patches, and verifying the build to ensure no new errors are introduced.

Can I use this to resolve import errors and lint blockers in a JavaScript project?

Yes, you can use this Skill to resolve import errors and lint blockers in JavaScript projects. It handles module resolution issues, fixes linter blockers, and corrects import/export problems by applying minimal edits to restore a clean build.

What is the best way to patch multi-language project builds with minimal safe fixes?

The best way to patch multi-language project builds is to automate error collection, categorize failures by severity, and apply minimal safe fixes. This process adds type annotations, resolves imports, and re-runs checks after each change to stop when the build passes.

Does this approach work for minor refactors needed to restore TypeScript builds?

Yes, this approach works for minor refactors needed to restore TypeScript builds. It strategically applies necessary minor refactors to resolve type errors and module resolution issues, ensuring the changes remain minimal and safe while achieving a green build.

Why should I use minimal fixes instead of large refactors to correct build failures?

You should use minimal fixes to correct build failures because they reduce the risk of introducing new errors. This approach applies targeted patches to type errors and lint blockers, verifying after each change to ensure stability and produce a green build safely.