build-fix

Detect build systems, parse first errors, and apply minimal fixes iteratively.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill build-fix-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-fix
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/build-fix
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill build-fix-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly fix failing builds by applying the smallest possible change that addresses the current error, then verifying again—without drifting into risky refactors.

Core Features & Use Cases

  • Build system detection & error parsing: Identifies the project’s build toolchain (Node/TS/Cargo/Go/Maven/Gradle/Python) and focuses on the first failing error.
  • Minimal fix workflow: Makes one error at a time, re-runs the build after each fix, and stops if the situation worsens.
  • Structured debugging escalation: When simple fixes fail, it switches to OBSERVE → HYPOTHESIZE → TEST → FIX, plus a 5 Whys loop for persistent failures.
  • Guardrails to prevent spec drift: Forces early returns to /plan or back to spec when architectural changes or contradictions are required.

Quick Start

Ask the agent to run the build for the repository, parse the first error, apply the smallest targeted fix, and repeat until both the build and tests pass.

Frequently Asked Questions about build-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix failing builds across different package managers like npm, Cargo, and Maven?

Fix failing builds by detecting the project toolchain, running the build, parsing the first error, and applying a minimal one-at-a-time patch. This workflow supports npm, Cargo, Go, Maven, Gradle, and Python, repeating until both build and tests pass.

What is the best way to resolve TypeScript or Python build errors without risky refactoring?

The best way to resolve build errors safely is applying the smallest possible change that addresses the current error, then verifying again. This prevents risky refactors and stops immediately if the build situation worsens or regresses.

How does structured debugging handle persistent build failures that simple fixes do not resolve?

Structured debugging handles persistent build failures by escalating to an OBSERVE, HYPOTHESIZE, TEST, and FIX loop. It also applies a 5 Whys loop for recurring errors and forces a return to the spec if architectural changes are required.

Does build troubleshooting stop if my incremental fixes cause test regressions?

Yes, build troubleshooting enforces deterministic iteration and stops if the situation worsens or causes test regressions. It requires final verification with both the build and tests passing before completing the workflow.

When should I avoid automated build error parsing and go back to the project spec?

You should avoid automated build error parsing and return to the project spec when resolving errors requires architectural changes or contradictions. The workflow enforces spec conformance and forces early returns to plan to prevent spec drift.