skills.rest
spideynolove
spideynoloveCOMMUNITY
Explore all skills by this author →
Website𝕏@spideynoloveGitHub

rlm-debugging

Diagnose root causes of bugs and test failures through a structured four-step debugging workflow.

2|3|Updated Mar 13, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#bug fixing#test failures#hypothesis testing#rlm workflow
One-click install
npx skills add https://github.com/spideynolove/claude-dotfiles --skill rlm-debugging-spideynolove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rlm-debugging
Source: https://github.com/spideynolove/claude-dotfiles/tree/main/.agents-global/skills/rlm-workflow/skills/rlm-debugging
Command: npx skills add https://github.com/spideynolove/claude-dotfiles --skill rlm-debugging-spideynolove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When fixing bugs or investigating test failures, ad-hoc guess-and-check fixes waste time and introduce new defects. This Skill enforces systematic root cause analysis before any fix is attempted, inserting a dedicated Phase 1.5 into the RLM workflow. ## Core Features & Use Cases - Root Cause Investigation: Read error messages, reproduce issues consistently, review recent changes, and trace data flow back to the source of bad values. - Pattern Analysis & Hypothesis Testing: Compare working versus broken code, form single hypotheses, and test them with minimal changes using the scientific method. - Structured Artifact Output: Produces a 01.5-root-cause.md document with coverage and approval gates that feeds directly into the Phase 2 fix plan. - Use Case: When tests fail after a change, trigger this Skill to document the error analysis, reproduction steps, and confirmed root cause before writing any fix. ## Quick Start Ask the AI to debug the failing tests using systematic root cause analysis and produce a root cause report before proposing any fix.

Frequently Asked Questions about rlm-debugging

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

FAQPage Schema
How do I debug failing tests systematically instead of guessing?▼

Follow the four-step process: investigate the root cause by reading errors and reproducing the issue, analyze patterns against working code, form and test a single hypothesis with minimal changes, then document the confirmed root cause before fixing.

What is root cause analysis in a debugging workflow?▼

Root cause analysis traces a bug back to its origin rather than patching symptoms. It involves reading error messages, verifying reproduction, reviewing recent changes, and tracing data flow backward through the call stack to find where the bad value originates.

When should I use systematic debugging instead of a quick fix?▼

Use it for any bug fix, test failure, or unexpected behavior, especially under time pressure or after previous fix attempts failed. Guessing is slower than systematic investigation, and symptom fixes typically create new bugs.

What should I do after three or more fix attempts have failed?▼

Stop attempting fixes and question the architecture. Repeated failures where each fix reveals new coupling or creates new symptoms indicate a fundamental design problem that needs refactoring rather than another symptom patch.

How do I debug failures in multi-component systems?▼

Add diagnostic instrumentation at each component boundary, logging what data enters and exits each layer. Run once to gather evidence showing where the failure occurs, then analyze which component boundary breaks before proposing fixes.

Related Skills

Explore More Software Engineering Skills→
tctinhtctinh
160

systematic-debugging

Guide structured four-phase debugging to identify root causes before code changes.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
rust-worksrust-works
51

testing

Identify and address common testing anti-patterns across software projects.

Official
Intermediate
davpatel605-beepdavpatel605-beep

python-debugpy

Debug Python runtime failures using pdb, debugpy, and DAP workflows.

Community
Advanced