build-fix

Diagnose and incrementally fix TypeScript and build errors in npm projects.

125|35|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/jh941213/my-claude-code-asset --skill build-fix-jh941213
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-fix
Source: https://github.com/jh941213/my-claude-code-asset/tree/main/skills/build-fix
Command: npx skills add https://github.com/jh941213/my-claude-code-asset --skill build-fix-jh941213

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers progressively identify and fix TypeScript and build errors during development and CI, reducing time spent on problematic builds.

Core Features & Use Cases

  • Incremental error diagnosis: group errors by severity and prioritize fixes
  • Guided fixes: propose code changes and commands to validate fixes
  • CI-friendly: smoothly integrates with npm/pnpm workflows for continuous builds

Quick Start

Run a local build to surface errors, then apply fixes incrementally:

  • npm run build
  • pnpm build
  • review errors, apply edits, and re-run the build

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 iteratively in an npm project?

To fix TypeScript build errors iteratively, run your build command like npm run build, analyze the grouped errors by severity, apply the suggested code edits, and re-run the build until the project compiles successfully.

What is the best way to diagnose multi-file TypeScript errors during local development?

Diagnosing multi-file TypeScript errors involves running a local build to surface all failures, reviewing the errors with their surrounding context, and progressively applying fixes across the affected files before validating again.

Can I use this approach to fix build errors in pnpm CI workflows?

Yes, you can fix build errors in pnpm CI workflows by running pnpm build, analyzing the output errors, and applying incremental fixes guided by the error severity grouping to ensure continuous builds compile smoothly.

Why should I group TypeScript errors by severity before applying fixes?

Grouping TypeScript errors by severity helps prioritize the most critical issues first, allowing for incremental fixes that systematically reduce the total number of build failures across multiple files without being overwhelmed.

What should I do if my TypeScript build keeps failing after applying suggested edits?

If your TypeScript build keeps failing, you should continue the iterative loop of analyzing the remaining errors with their surrounding context, applying the next proposed code changes, and re-running the build until it compiles.