build-fix
Use to auto-resolve build errors. Reads compiler/linker/bundler output, classifies, suggests minimal-diff fixes. Different from /heal (which is multi-strategy retry across build/test/lint).
What this skill does
# build-fix Single-purpose: build is failing, you want it green with the smallest possible diff. ## Method 1. **Capture full build output.** Stdout + stderr from the failing command. 2. **Classify** the first failure (later failures often cascade from first): - **Type error** (TS / Flow) → narrow to file:line, propose annotation/cast/refactor - **Module not found** → missing dep / wrong import path / case mismatch - **Syntax error** → fix the file:line directly - **Linker / native binding** → check rebuild scripts, postinstall - **Bundler config** → tsconfig / vite.config / webpack.config issue - **Codegen** → schema/proto/openapi out of date 3. **Hypothesise minimal-diff fix.** 4. **Apply.** 5. **Re-run build.** Pass → done. Fail → if same error after distinct strategy, escalate via `/heal`. 6. **Categorise for memory.** Future `build-fix` runs hit the cache for the same error class. ## Output shape ``` Build cmd: <command> Output (head): <first 30 lines> Classification: <type error | module not found | syntax | linker | config | codegen> Fault: <file:line> Hypothesis: <one-line> Fix: <minimal diff> Re-run: Status: ✓ build green | ✗ same error | ✗ new error If new error: chained build-fix run If same error: escalate to /siftcoder:heal (multi-strategy) Captured: <memory id — error → fix mapping> ``` ## Rules - **Minimal diff.** Adding `// @ts-ignore` is a smell, not a fix — only acceptable with reason in commit message. - **One error at a time** (cascade pruning — first error often unblocks others). - **Don't loop on same strategy.** Cap at 2 attempts; escalate. - **Memory captures error→fix.** Repeat builds hit the cache. - **No silent type weakening.** If a fix involves casting to `any`, surface explicitly to user. ## Anti-patterns - Mass `// @ts-ignore` to make build pass - Bumping a dep to "any version that works" without reading changelog - Disabling the failing rule in eslint config instead of fixing the code - Touching unrelated files because "they were also broken" ## When NOT to use - Multi-strategy auto-recovery → `/siftcoder:heal` - Test failures (not build) → `/siftcoder:fix` or `/heal` - Architecture-shaped problem (build broken because design is wrong) → `/investigate` first ## Subagent dispatch - `Bash` to run build - `Explore` to find the fault location - `general-purpose` for the diff - Memory MCP for prior similar errors ## Value over native CC CC will fix build errors on request. CC doesn't always classify error class first, doesn't enforce minimal-diff discipline, won't refuse type-weakening shortcuts. The discipline IS the value.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.