build-fix

Diagnose and fix build and TypeScript errors with minimal diffs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill build-fix-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-fix
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/build-fix
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill build-fix-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes build and compilation errors quickly with minimal code changes, enabling projects to compile and run again without large refactors.

Core Features & Use Cases

  • Collects compiler and type-check errors across common languages by running standard project commands (e.g., tsc, go build, cargo check).
  • Proposes minimal-diff fixes focused on types, imports, and small code adjustments to restore build.
  • Verifies fixes by re-running the build and type checks, stopping when the project passes.

Quick Start

Initiate the build-fix workflow to collect errors, apply minimal-diff changes, and re-run the build until it passes.

Frequently Asked Questions about build-fix

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 fix TypeScript build errors automatically by using a sub-agent workflow that collects compiler errors, applies minimal-diff patches to types and imports, and verifies the build passes. This restores compilation without large refactors.

Can I use this to diagnose webpack and eslint build failures?

Yes, you can diagnose webpack and eslint build failures. The workflow runs standard project commands to collect errors from these tooling environments, proposes minimal code adjustments, and re-runs checks until the project passes.

Does this build fix workflow require specific dependencies or components?

No specific dependencies or components are required. You only need a standard software project with existing build scripts and type checkers like tsc or go build for the workflow to collect errors and apply patches.

What's the best way to resolve compiler and type-check errors across different languages?

The best way to resolve compiler and type-check errors is automating the collection of errors from standard commands like tsc and cargo check, then generating minimal-diff fixes focused on small code adjustments to restore the build.

Why does the automated build fix process re-run the build after applying patches?

The automated build fix process re-runs the build to verify that the minimal-diff patches successfully resolved the errors. It repeats this verification cycle, stopping only when the project passes the build and type checks.