skills.rest
deepklarity
deepklarityOFFICIAL
Explore all skills by this author →
Website𝕏@DeepKlarityGitHub

dk-rca

Guide seven-step root-cause analysis from reproduction through documentation.

87|12|Updated Mar 1, 2026
Search Tags:#debugging#verification#protocol#reproduce#hypothesis#root-cause-analysis
One-click install
npx skills add https://github.com/deepklarity/harness-kit --skill dk-rca
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dk-rca
Source: https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/dk-rca
Command: npx skills add https://github.com/deepklarity/harness-kit --skill dk-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging often skips essential reasoning steps, leading to unresolved failures. This skill enforces a disciplined root-cause analysis protocol that gates each step to ensure thorough investigation.

Core Features & Use Cases

  • Seven-step RCA protocol: Reproduce, Locate, Hypothesis, Failing Test, Fix, Verify Live, Document.
  • Guardrails for debugging: Requires explicit hypothesis before proposing a fix and records evidence for each step.
  • Use Case: When something is broken, use this skill to structure and validate your debugging process end-to-end.

Quick Start

Describe the bug context and trigger the RCA protocol to begin the step-by-step analysis.

Frequently Asked Questions about dk-rca

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

FAQPage Schema
How do I structure root-cause analysis during debugging to avoid skipping reasoning steps?▼

Root-cause analysis during debugging is structured using a seven-step protocol: reproduce, locate, hypothesis, failing test, fix, verify live, and document. This enforces hypothesis-first reasoning and step-by-step verification to diagnose failures thoroughly.

What is the best way to enforce a hypothesis before proposing a bug fix?▼

The best way to enforce a hypothesis before a bug fix is using a guided RCA protocol with guardrails. It requires an explicit hypothesis and records evidence for each debugging step, preventing fixes from being applied without thorough investigation.

How do I start a step-by-step debugging investigation when a failure occurs?▼

To start step-by-step debugging, describe the bug context and trigger the RCA protocol. You then progress sequentially through reproduce, locate, hypothesis, failing test, fix, verify live, and document steps to resolve the unexpected outcome.

When should I use a structured RCA protocol instead of ad-hoc debugging?▼

You should use a structured RCA protocol when debugging unexpected outcomes or conducting failure investigations. It gates each step to ensure thorough investigation, preventing the essential reasoning steps often skipped during ad-hoc debugging that lead to unresolved failures.

Does root-cause analysis require a failing test before applying a fix?▼

Yes, root-cause analysis requires a failing test before applying a fix. The seven-step protocol explicitly gates the fix step behind the failing test step, ensuring the hypothesis is validated through testing before any code changes are made.

Related Skills

Explore More Software Engineering Skills→
fluxforgeaifluxforgeai
3

investigate

Perform hypothesis-driven root cause analysis and generate investigation reports.

Community
Advanced
pierreribeiropierreribeiro

debug-investigator

Automate root-cause analysis with 5 Whys and RCA reports.

Community
Basic
mopeyjellyfishmopeyjellyfish
1

debug

Reproduce bugs from evidence and prove root causes with red signals.

Community
Advanced
brittaniebuffiecsubrittaniebuffiecsu
1

mcporter

Manage MCP server connections, authentication, configuration, and function calls via CLI.

Community
Intermediate