| name | rca-bugfix |
| description | Root cause analysis and bug fix procedure. Investigates bugs, documents the RCA, and creates an implementation prompt for the fix. Use after /investigate or /finding. |
| disable-model-invocation | false |
| argument-hint | [finding-ref or description] |
| effort | xhigh |
| wrought | {"version":"1.0","tools":{"capabilities":["read_file","search_content","find_files","write_file","edit_file","run_command"]},"platforms":{"claude-code":{"disable-model-invocation":false}},"agent":{"role":"RCA Engineer","expertise":["root cause analysis","bug fixing","implementation planning"],"non_goals":["architectural redesign","feature development"]},"execution":{"default_mode":"hypothesis-rca","optional_modes":["self-refine"],"max_iterations":12,"max_refine":1,"stop_conditions":["RCA document written to docs/RCAs/","Implementation prompt written to docs/prompts/","User instructed to stop"]},"output":{"format":"markdown","template":"docs/RCAs/{YYYY-MM-DD_HHMM}_{name}.md","required_sections":["Summary","Root Cause","Evidence","Fix","Verification"],"prohibited_content":["credentials","secrets"]},"pipeline":{"track":"reactive","standalone":false,"prerequisites":["docs/investigations/*.md","docs/findings/*.md"],"produces":["docs/RCAs/*.md","docs/prompts/*.md"],"suggested_next":["plan"]}} |
RCA Bug Fix Procedure
Trigger: Use /rca-bugfix {issue description} when investigating and fixing bugs that require root cause analysis.
Examples:
/rca-bugfix health check timeout causing gray indicators on monitor page/rca-bugfix rate limiting still happening despite batch processing implementation/rca-bugfix extractions stuck at 0 records during streaming
Prerequisites
Before executing this skill, verify ALL of the following:
- Use Glob to check for:
docs/investigations/*.md
- If NO match -> STOP: "Run /investigate first to create an investigation report."
- If user says
--force, proceed without validation.
- Read the most recent Findings Tracker matching
*_FINDINGS_TRACKER.md
- Identify the relevant finding (ask user if ambiguous)
Pre-flight Check
- Verify artifact prerequisites (above)
- Identify which finding/workflow this is for
- Load finding report and related artifacts for context
- Proceed to main skill instructions
Instructions
The user has provided an issue to investigate. Reason thoroughly about this issue — trace the root cause through evidence before proposing a fix.
Issue to investigate: The argument passed after /rca-bugfix
Input Sources
Before starting, check for upstream artifacts: docs/investigations/*.md (from /investigate), docs/findings/*.md (from /finding), or work from the user-provided description. When a finding report provides a known cause, focus on confirming it, defining the fix, and writing the implementation prompt.
CRITICAL: File Naming Convention
ALL files MUST use this exact format: {YYYY-MM-DD_HHMM}_{issue_name}.md
✅ 2026-01-22_1700_stream_download_timeout.md
❌ RCA_STREAM_DOWNLOAD_TIMEOUT_2026-01-22.md — no prefix, date comes FIRST
Context Check
See context_check.md
