Slash Command

/build-fix

Diagnoses build system, parses and groups errors, incrementally fixes them one-by-one with minimal changes, verifies each fix, and summarizes results.

Typescript

Node

From shipshape-skills

Install

Run in your terminal

npx claudepluginhub mukiwu/muki-ai-plugins --plugin shipshape-skills

Command Content

Other plugins with /build-fix

/build-fix

Detects build system and incrementally fixes build/type errors with minimal changes, verifying each fix and summarizing results with fixed/remaining errors.

ecc

140.7k

/build-fix

Incrementally fixes Python type errors (mypy), lint issues (ruff), and failing tests (pytest) one by one: explains issues, applies fixes, verifies resolution, and shows summaries of results.

claude-scholar

3.1k

/build-fix

Automatically analyzes and fixes build errors (syntax, type, dependencies, config). Runs tests/builds for verification, retries up to 3x, and reports results with changes or recommendations.

ReadGlobGrep+3

tsumiki

934

/build-fix

Incrementally fixes TypeScript and build errors one at a time: runs build, parses output by file/severity, applies targeted fixes with context/explanation/verification, and summarizes results.

claude-forge

605

/build-fix

Autonomously fixes dotnet build errors: parses compiler output, categorizes issues, applies targeted fixes, and rebuilds up to 5 times until green or limit reached.

dotnet-claude-kit

188

/build-fix

Detects build system, runs build to identify errors, then iteratively fixes build and type errors with minimal safe changes, verifying each fix and summarizing results.

everything-claude-code

Stats

Parent Repo Stars16

Parent Repo Forks2

Last CommitMar 24, 2026

Actions

View Source View Plugin View on GitHub View README

Build and Fix

Incrementally fix build and type errors with minimal, safe changes.

Step 1: Detect Build System

Identify the project's build tool and run the build:

Indicator	Build Command
`package.json` with `build` script	`npm run build` or `pnpm build`
`tsconfig.json` (TypeScript only)	`npx tsc --noEmit`
`Cargo.toml`	`cargo build 2>&1`
`pom.xml`	`mvn compile`
`build.gradle`	`./gradlew compileJava`
`go.mod`	`go build ./...`
`pyproject.toml`	`python -m py_compile` or `mypy .`

Step 2: Parse and Group Errors

Run the build command and capture stderr
Group errors by file path
Sort by dependency order (fix imports/types before logic errors)
Count total errors for progress tracking

Step 3: Fix Loop (One Error at a Time)

For each error:

Read the file — Use Read tool to see error context (10 lines around the error)
Diagnose — Identify root cause (missing import, wrong type, syntax error)
Fix minimally — Use Edit tool for the smallest change that resolves the error
Re-run build — Verify the error is gone and no new errors introduced
Move to next — Continue with remaining errors

Step 4: Guardrails

Stop and ask the user if:

A fix introduces more errors than it resolves
The same error persists after 3 attempts (likely a deeper issue)
The fix requires architectural changes (not just a build fix)
Build errors stem from missing dependencies (need npm install, cargo add, etc.)

Step 5: Summary

Show results:

Errors fixed (with file paths)
Errors remaining (if any)
New errors introduced (should be zero)
Suggested next steps for unresolved issues

Recovery Strategies

Situation	Action
Missing module/import	Check if package is installed; suggest install command
Type mismatch	Read both type definitions; fix the narrower type
Circular dependency	Identify cycle with import graph; suggest extraction
Version conflict	Check `package.json` / `Cargo.toml` for version constraints
Build tool misconfiguration	Read config file; compare with working defaults

Fix one error at a time for safety. Prefer minimal diffs over refactoring.