Xpersona
S

Systematic Debugging

CLAWHUB · Unverified

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Skill: Systematic Debugging Owner: runesleo Summary: Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Tags: debugging:3.0.0, developer-tools:3.0.0, latest:3.0.0, workflow:3.0.0 Version history: v3.0.0 | 2026-03-07T13:41:56.061Z | auto - Major update: Introduces a comprehensive four-phase (plus pre-phase) debugging process focused on root cause anal

62
Rank
84
Safety
12k
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 12.1K downloads reported by the source. Last updated 11/16/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s17610fgthy0xhqwnxhhxv230x884fvk:runesleo-systematic-debugging
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-runesleo-runesleo-systematic-debugging-ebugging-2/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

12,269 characters of source documentation, loaded on request.

Extracted files

3 files captured from the source.

SKILL.md

---
name: Systematic Debugging
description: Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
when_to_use: when encountering any bug, test failure, or unexpected behavior, before proposing fixes
version: 3.0.0
languages: all
attribution: Based on obra/superpowers-skills (MIT License). Phase 0 and additional patterns added.
---

# Systematic Debugging

## Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of debugging.**

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
NO INVESTIGATION WITHOUT CONTEXT RECALL FIRST
```

If you haven't completed Phase 0, you cannot proceed to Phase 1.
If you haven't completed Phase 1, you cannot propose fixes.

## When to Use

Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues

**Use this ESPECIALLY when:**
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue

**Don't skip when:**
- Issue seems simple (simple bugs have root causes too)
- You're in a hurry (rushing guarantees rework)
- Manager wants it fixed NOW (systematic is faster than thrashing)

## The Five Phases

You MUST complete each phase before proceeding to the next.

### Phase 0: Context Recall (MANDATORY FIRST STEP)

**BEFORE doing ANYTHING else:**

1. **Extract Keywords from Error**
   - What's the error type? (OOM, timeout, connection, type error...)
   - What component? (server, browser, API, database...)
   - What area of the codebase?

2. **Search for Prior Knowledge**
   - Check project docs, MEMORY files, or past conversations
   - Search codebase for similar error patterns: `grep -r "ErrorType" .`
   - Check git log for related recent changes: `git log --oneline -20`

3. **Review Results**
   - Found relevant experience? -> **Apply directly, skip to Phase 4**
   - Found partial match? -> Use as starting point for Phase 1
   - Nothing found? -> Proceed to Phase 1, **remember to record solution later**

4. **Output Format**
   ```
   Context Recall:
   - Query: "xxx"
   - Found: [description of related knowledge]
   - Action: [apply experience / continue investigation / no match]
   ```

**VIOLATION:** Proceeding to Phase 1 without Context Recall output = process failure.

---

### Phase 1: Root Cause Investigation

**BEFORE attempting ANY fix:**

1. **Read Error Messages Carefully**
   - Don't skip past errors or warnings
   - They often contain the exact solution
   - Read stack traces completely
   - Note line numbers, file paths, error codes

2. **Reproduce Consistently**
   - Can you trigger it reliably?
   - What a

_meta.json

{
  "ownerId": "kn73j8znzcr6s9ejfe069g30b182f63h",
  "slug": "runesleo-systematic-debugging",
  "version": "3.0.0",
  "publishedAt": 1772890916061
}

skill-card.md

## Description:

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

This skill is ready for commercial/non-commercial use.

## Publisher:

[runesleo](https://clawhub.ai/user/runesleo)

### License/Terms of Use:


## Use Case:

Developers and engineering agents use this skill when investigating bugs, test failures, build failures, performance problems, integration issues, or other unexpected technical behavior. It guides the agent to recall relevant context, identify root cause, compare working patterns, test a focused hypothesis, and implement a verified fix.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill directs agents to check memory files or past conversations before debugging, which can expose unrelated sensitive history.

Mitigation: Restrict context recall to the current project unless the user explicitly approves broader memory, conversation, or shared-workspace access.

## Reference(s):


## Skill Output:

**Output Type(s):** [guidance, markdown, shell commands]

**Output Format:** [Markdown with structured debugging steps and inline shell commands]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May produce context-recall summaries, root-cause hypotheses, diagnostic commands, test plans, and implementation guidance.]

## Skill Version(s):

3.0.0 (source: frontmatter and server-resolved release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Sponsored

Ads related to Systematic Debugging and adjacent AI workflows.