​

/build-fix Command

​

What This Command Does

1. Detect Build System - Identify project type and build command
2. Parse and Group Errors - Group by file, sort by dependency order
3. Fix Loop - Fix one error at a time, verify after each
4. Summary - Report errors fixed, remaining, and new errors

​

Supported Build Systems

​

Fix Strategy

1. Build errors first - Code must compile
2. Vet warnings second - Fix suspicious constructs
3. Lint warnings third - Style and best practices
4. One fix at a time - Verify each change
5. Minimal changes - Don’t refactor, just fix

​

Fix Loop Process

1. Read the file - See error context (10 lines around error)
2. Diagnose - Identify root cause
3. Fix minimally - Smallest change that resolves error
4. Re-run build - Verify error is gone
5. Move to next - Continue with remaining errors

​

Command Syntax

/build-fix

​

Example Session

# Initial Build
$ npm run build

Error: Type 'string' is not assignable to type 'number'
  src/utils/calc.ts:25:15

Error: Cannot find name 'User'
  src/api/users.ts:42:9

Total: 2 errors

# Fix 1: Type Mismatch
File: src/utils/calc.ts:25
Changing: count = params.get("count")
To: count = Number(params.get("count"))

$ npm run build
Remaining: 1 error

# Fix 2: Missing Import
File: src/api/users.ts:42
Adding: import { User } from "./types"

$ npm run build
Build successful! ✅

# Summary
- Errors fixed: 2
- Files modified: 2
- Remaining issues: 0

​

Common Errors Fixed

​

Stop Conditions

• Same error persists after 3 attempts
• Fix introduces more errors than it resolves
• Requires architectural changes (not just a build fix)
• Missing external dependencies need installation

​

Integration with Other Commands

• Use after making code changes
• Use before running tests with /verify
• Language-specific: /go-build for Go projects

​

Related

• Agent: agents/build-error-resolver.md
• Commands: /go-build, /verify, /tdd