Agent skill · Workflow & Productivity

dev-buddy-rca

Root cause analysis for bugs. Dispatches RCA executors in parallel, consolidates findings, and appends RCA Diagnosis to the plan file.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill dev-buddy-rca --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBashGlobGrepTaskTaskOutputAskUserQuestion
Path: skills/analysis/dev-buddy-rca/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# RCA Stage Skill Diagnose a bug by dispatching root cause analysis executors. Consolidates findings and appends the RCA Diagnosis section to the plan file. --- ## Step 1: Load Config and Resolve Executors ```bash bun -e " import { loadDevBuddyConfig, getProviderType } from '${CLAUDE_PLUGIN_ROOT}/scripts/pipeline-config.ts'; const config = loadDevBuddyConfig(); const stage = config.stages['rca']; const executors = stage.executors.map(exec => ({ ...exec, providerType: getProviderType(exec.preset) })); console.log(JSON.stringify({ executors })); " ``` --- ## Step 2: Resolve Session Variables 1. Resolve tmpdir: ```bash bun -e "console.log(require('os').tmpdir())" ``` Store as `{TMPDIR}`. 2. Generate unique output IDs: ```bash bun -e "console.log(require('crypto').randomBytes(4).toString('hex'))" ``` Store as `{RAND}`. Output file for executor at index `{i}`: `{TMPDIR}/.vcp/oneshot/rca-{RAND}-{i}.json` 3. Ensure output directory: ```bash mkdir -p "{TMPDIR}/.vcp/oneshot" ``` --- ## Step 3: Prompt Assembly For each RCA executor: ``` ORIGINAL REQUEST: {user's bug description from conversation} --- You are executing the ROOT CAUSE ANALYSIS stage. Diagnose the bug described above. Do NOT fi

What's inside
Steps it walks through
  1. Step 1: Load Config and Resolve Executors
  2. Step 2: Resolve Session Variables
  3. Step 3: Prompt Assembly
  4. Step 4: Dispatch Executors
  5. Step 5: Collect and Consolidate
  6. Step 6: Append RCA Diagnosis to Plan File
  7. Step 7: Cleanup and Report
  8. Error Handling
Ships with 1 file
  • metadata.json
Commands it runs
bun -e "
import { loadDevBuddyConfig, getProviderType } from '${CLAUDE_PLUGIN_ROOT}/scripts/pipeline-config.ts';
const config = loadDevBuddyConfig();
const stage = config.stages['rca'];
const executors = stage.executors.map(exec => ({
bun -e "console.log(require('os').tmpdir())"
bun -e "console.log(require('crypto').randomBytes(4).toString('hex'))"
mkdir -p "{TMPDIR}/.vcp/oneshot"
import { loadStageDefinition, getSystemPrompt, composePrompt } from '${CLAUDE_PLUGIN_ROOT}/scripts/system-prompts.ts';
const stage = loadStageDefinition('rca', '${CLAUDE_PLUGIN_ROOT}/stages');
More from claude-skill-registry
All skills →
About this skill
What does the dev-buddy-rca skill do?

Root cause analysis for bugs. Dispatches RCA executors in parallel, consolidates findings, and appends RCA Diagnosis to the plan file.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill dev-buddy-rca --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.

Keep going