root-cause-analysis-and-fix
This skill is for debugging failed Bauplan runs. It assumes a failure has already occurred and prioritizes evidence collection before any change.
npx skills add majiayu000/claude-skill-registry --skill root-cause-analysis-and-fix --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
--- name: root-cause-analysis-and-fix description: “Inspect a failed Bauplan pipeline run on a dev branch, reconstruct the frozen data state, collect evidence, propose a minimal code fix using Git, and rerun deterministically where possible.” allowed-tools: • Bash(bauplan:*) • Bash(git) • Read • Write • Glob • Grep • WebFetch(domain:docs.bauplanlabs.com) --- # Root Cause Analysis and Fix (Data + Code) This skill is for debugging failed Bauplan runs. It assumes a failure has already occurred and prioritizes evidence collection before any change. Data state is controlled by Bauplan data refs. Code state is controlled by Git. Both must be treated explicitly. ## CRITICAL RULES 1. NEVER run or write anything on main (Bauplan or Git). 2. NEVER change code without Git version control. 3. NEVER inspect data on a moving ref. All queries must target an explicit ref (branch@[commit_hash] or tag). 4. NEVER rerun blindly. Always inspect the frozen failing state first. 5. Keep debug branches open until the issue is understood. Do not clean up unless explicitly asked by the user. If any rule cannot be satisfied, STOP and REPORT the blocker. ## Required Inputs You need at least one of the followin
- CRITICAL RULES
- Required Inputs
- Step 0: Establish safety boundaries (Bauplan and Git)
- 0A. Confirm you are not on Bauplan main
- 0B. Confirm Git prerequisites
- Step 1: Identify the frozen data ref for the failed job
- 1A. If you have a job id
- 1B. Map job to a commit hash
- Step 2: Create a Bauplan debug branch from the failing ref
- Step 3: Establish Git code provenance
- 3A. Determine whether code is pinned
- 3B. Create a Git debug branch
- Step 4: Collect evidence (before any fixes)
- 4A. Code evidence
bauplan info bauplan checkout -branch <username>.debug_<short_name>
What does the root-cause-analysis-and-fix skill do?
This skill is for debugging failed Bauplan runs. It assumes a failure has already occurred and prioritizes evidence collection before any change.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill root-cause-analysis-and-fix --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.