agentsclimarketplace

Build debug

Skill sh-ai-x/dev-harness-kit/skills/build-debug

4-phase systematic debugging. No fix proposal before Phase 1 (reproduce) completes (MUST-L2). Root-cause-first Iron Law. Standalone invocation hands the root cause to /dev-kit:plan instead of fixing inline.From its SKILL.md

Install
npx -y skills add sh-ai-x/dev-harness-kit --skill build-debug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.3 KB, as published. Nobody here has run it

← Skills index

build-debug — Systematic Debugging (4 Phase)

Iron Law

No fix proposal before Phase 1 (reproduce) completes.

Two invocation contexts

Phases 1-3 (reproduce → isolate → root cause) are identical either way. Phase 4 branches on context:

In-build self-fix loopStandalone (top-level)
Triggermodel auto-invokes mid-step, inside an already-reviewed build step (lib/execute.py's 3-cycle self-fix guard)user types /dev-kit:build-debug <bug description>, or the model reasons a bug report needs root-cause-first investigation with no build step running
Phase 4fixes inline with a regression test (Iron Law L1: no test = no fix)hands the quoted root cause to /dev-kit:plan via Skill("plan", ...); does NOT patch code
Reviewed before code changes?no — it's already inside a reviewed stepyes — /dev-kit:plan's Gate 5/5 stops at the auto-rendered proposal.html and waits for the user to explicitly type /dev-kit:build

The standalone path exists because there was no top-level command for "here's a bug report, root-cause it and plan a proper fix with a reviewable proposal" — before this, a user who found a bug with no build step running had to invent the reproduce/root-cause discipline by hand, or jump straight from "found a bug" to editing code with no PRD, no proposal, no review.

Optional Linear preflight

At the start of a new debugging task, invoke /dev-kit:linear once when Linear is enabled or available. Continue normally on LINEAR_SKIP or an implicit LINEAR_ERROR; do not invoke it between debugging phases. See skills/linear/SKILL.md for the reconciliation contract.

4 Phases (separate cycles)

[1/4] REPRODUCE  → 1+ failing cases
       (don't proceed if reproduction fails)
       ↓
[2/4] ISOLATE    → minimal reproduction
       (reduce input / block external deps)
       ↓
[3/4] ROOT CAUSE → specific line + call stack quoted
       (tools: git blame, git bisect, log, debugger)
       ↓
[4/4] FIX or PLAN HAND-OFF
       in-build:    fix with a regression test (Iron Law L1: no test = no fix)
       standalone:  Skill("plan", <bug summary + root cause>) — no code written here

Rules (no exceptions)

  • Do not bundle 4 phases into one cycle (MUST-NO-LOOP).
  • User confirmation after each phase, or 4 phases in separate calls.
  • Asserting "probably X" without root cause quoted ❌.
  • One change at a time. Multiple changes at once ❌.
  • Standalone Phase 4 refuses to write a regression test, patch source, or invoke /dev-kit:build//dev-kit:build-tdd directly — that work is scoped and reviewed by /dev-kit:plan first.

Hook integration

tdd-guard is ON during build stage. Writing a fix during the in-build Phase 4 forces a regression test to accompany it. The standalone Phase 4 never reaches tdd-guard — it writes no code.

Hand-off

In-build self-fix loop, after 4 phases:

  • Quote root cause in 1 line + regression test GREEN
  • state_codec.append_hand_off(root, "build", "build", "..")
  • Loop back to the per-step harness runner (lib/execute.py)

Standalone, after Phase 4's plan hand-off:

  • Skill("plan", <bug summary + root cause>) — the quoted root cause (file:line + call stack) becomes Gate 1's situation field and Gate 2's evidence signal.
  • /dev-kit:plan runs its full 5-gate loop and, at Gate 5/5, emits PRD.md + phases/<name>/ and auto-renders docs/proposals/<main>/<sub>.html. This skill's job ends there.

Red Flags

ThoughtReality
"Probably X"Unknown if not reproduced
"Just patch it"Ignoring root cause → same bug repeats
"Multiple changes at once"Can't tell which change was the fix
"Skip reproduce"L2 violation

Keep looking

Skills are one crate of 608,666. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.