build-fix

Resolve build, TypeScript, and lint errors incrementally in a codebase.

1|1|Updated Feb 1, 2026

Search Tags:#code quality #automation #typescript #linting #debugging #build

Ready to run

npx skills add https://github.com/corbat-tech/coco --skill build-fix-corbat-tech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-fix
Source: https://github.com/corbat-tech/coco/tree/main/.claude/skills/build-fix
Command: npx skills add https://github.com/corbat-tech/coco --skill build-fix-corbat-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious and time-consuming process of fixing build, TypeScript, and linting errors in a codebase, ensuring a clean and functional state.

Core Features & Use Cases

Incremental Error Resolution: Addresses errors one by one, ensuring minimal and safe changes.
Error Prioritization: Fixes import errors, then type errors, then lint errors, and finally test failures.
Use Case: After a code merge, a project fails its build due to numerous TypeScript errors. This Skill can be invoked to systematically resolve these errors, allowing the build to pass without manual intervention.

Quick Start

Use the build-fix skill to resolve all build and type errors in the project.

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?▼

Fix TypeScript build errors automatically by detecting error types and resolving root causes incrementally. The process targets import issues, type mismatches, and lint violations, then re-runs checks to ensure a clean build with minimal, safe changes.

What is the best way to resolve linting and unhandled promise errors in a codebase?▼

Resolving linting and unhandled promise errors involves prioritizing import errors first, then type errors, then lint errors. This systematic approach fixes root causes and re-runs checks to guarantee a functional state without manual intervention.

How do I fix missing file extensions in TypeScript imports?▼

Fix missing file extensions in TypeScript imports by detecting the import error type and applying minimal corrective changes. The resolution process handles CommonJS usage and import path issues before moving on to type and lint checks.

Can I resolve explicit any types and unchecked indexed access errors incrementally?▼

Resolve explicit any types and unchecked indexed access errors incrementally by fixing root causes one by one. This method ensures safe changes, prioritizing type errors after import issues to maintain a clean and functional codebase.

Does automated build fixing work for test failures after a code merge?▼

Automated build fixing works for test failures by prioritizing them last in the resolution process. After fixing import, type, and lint errors, the system addresses test failures to ensure the complete build passes.

What are the limitations of automated lint error resolution?▼

The limitation of automated lint error resolution is that it applies minimal, safe changes by fixing root causes incrementally. It prioritizes import and type errors first, meaning complex lint issues may require manual review if they fall outside common patterns.