Perform systematic root cause analysis for software bugs and failing tests.
npx skills add https://github.com/doubleuuser/rlm-workflow --skill rlm-debugging
Please help me install this Agent Skill. Skill: rlm-debugging Source: https://github.com/doubleuuser/rlm-workflow/tree/main/skills/rlm-debugging Command: npx skills add https://github.com/doubleuuser/rlm-workflow --skill rlm-debugging
This Skill prevents guesswork and symptom-based fixes by enforcing a structured Phase 1.5 root cause investigation that captures error analysis, reproduction steps, evidence, and a documented fix strategy before any code changes are attempted.
Start Phase 1.5 by creating a 01.5-root-cause.md artifact and follow the prescribed error analysis, reproduction, evidence gathering, hypothesis testing, and summary steps to produce a locked root cause report for Phase 3.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for failing CI tests requires documenting error messages, reproduction steps, recent changes, data-flow traces, and hypothesis tests before attempting fixes. This process produces a locked Phase 1.5 artifact that feeds directly into your subsequent fix plan.
Investigating intermittent crashes and performance regressions involves a structured template capturing error analysis, reproduction verification, evidence gathering, and hypothesis testing. This enforces a defensive workflow ensuring root causes are confirmed before any code modifications proceed.
Tracing data-flow to find root causes of incorrect API responses involves pattern comparison and hypothesis testing within a structured artifact. This prevents symptom-based fixes by requiring evidence and reproduction verification before moving to implementation.
This debugging workflow requires no specific dependencies or components to investigate CI failures. It provides a ready artifact layout and defines coverage gates to ensure tests are created and root causes are confirmed before proceeding to implement fixes.
A Phase 1.5 artifact for bug fixing is needed before implementing code changes and contains error analysis, reproduction steps, recent changes review, data-flow tracing, hypothesis tests, and a final root cause summary to guide the fix strategy.
Documenting reproduction steps and recent changes before fixing integration issues prevents guesswork by enforcing a structured root cause investigation. This defensive workflow defines approval gates to ensure causes are confirmed and tests are created prior to code changes.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
aziglerFix identified bugs with mandatory regression guard tests.
mwayIdentify root causes of bugs and test failures through a four-phase debugging workflow.
dudedesi12Integrate Sentry error tracking and structured logging in Next.js applications.
