skills.rest
robertolopezlopez
robertolopezlopezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

diagnose

Diagnose software bugs through reproducible debugging workflows and root cause analysis.

1|1|Updated Mar 26, 2026
Search Tags:#debugging#root cause#instrumentation#software testing#bug diagnosis#regression analysis
One-click install
npx skills add https://github.com/robertolopezlopez/agent-skills --skill diagnose-robertolopezlopez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/robertolopezlopez/agent-skills/tree/main/skills/core/diagnose
Command: npx skills add https://github.com/robertolopezlopez/agent-skills --skill diagnose-robertolopezlopez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers systematically investigate concrete bugs, flaky failures, and performance regressions instead of jumping directly to fixes without evidence.

Core Features & Use Cases

  • Reproduction-Driven Debugging: Builds narrow, reliable feedback loops from failing tests, commands, error reports, or regression signals.
  • Hypothesis and Instrumentation Workflow: Guides engineers through ranking hypotheses, collecting targeted evidence, and confirming root causes.
  • Use Case: When a production issue causes intermittent failures, use this Skill to create a reproducible scenario, analyze likely causes, validate findings, and define a regression-safe fix.

Quick Start

Use the diagnose skill to investigate this failing test, identify the root cause, and recommend the next debugging steps.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I find the root cause of a flaky test failure?▼

Find the root cause of flaky test failures by building narrow, reproducible feedback loops, ranking hypotheses, collecting targeted instrumentation evidence, and confirming the root cause through structured validation steps.

What's the best way to debug software regressions systematically?▼

Debug software regressions systematically by applying a disciplined debugging workflow that requires reproduction loops, hypothesis ranking, targeted instrumentation, and evidence-based validation before jumping directly to fixes.

How do I investigate performance regressions without guessing the fix?▼

Investigate performance regressions without guessing by creating a reproducible scenario, analyzing likely causes through hypothesis ranking, collecting targeted evidence, and confirming root causes before defining a regression-safe fix.

Can I use this debugging workflow for intermittent production issues?▼

You can use this debugging workflow for intermittent production issues by creating a reproducible scenario from error reports or regression signals, analyzing likely causes, validating findings, and defining a regression-safe fix.

What debugging artifacts do I need for a proper root cause analysis?▼

Proper root cause analysis requires debugging artifacts that document structured repro loops, ranked hypotheses, targeted instrumentation evidence, and validation steps confirming the identified root cause.

Related Skills

Explore More Software Engineering Skills→
rabbicserabbicse

bug-reproduction

Convert vague bug reports into minimal reproductions and failing regression tests.

Community
Advanced
a29paula29paul
1

gstack-openclaw-investigate

Enforce root cause investigation before bug fixes in software debugging workflows.

Community
Advanced
cchrisvcchrisv

diagnose

Diagnose software bugs and performance regressions through structured reproduction and validation workflows.

Community
Advanced
SamyakJhaveriSamyakJhaveri

diagnose

Guide a phase-based debugging loop from reproduction to validated fix.

Community
Advanced