skills.rest
swghosh
swghoshCOMMUNITY
Explore all skills by this author →
Website𝕏@SwG_GhoshGitHub

diagnose

Diagnose software bugs through evidence-based root cause analysis.

Updated May 5, 2026
Search Tags:#debugging#root cause analysis#hypothesis testing#regression testing#code tracing#git blame#incident documentation
One-click install
npx skills add https://github.com/swghosh/ambient-workflows --skill diagnose-swghosh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/swghosh/ambient-workflows/tree/main/workflows/bugfix/.claude/skills/diagnose
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill diagnose-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you move from observed failures to an evidence-based root cause, so you can fix the underlying issue rather than patch symptoms.

Core Features & Use Cases

  • Evidence-based root cause analysis: Reviews reproduction conditions, traces execution flow, and ties conclusions to concrete artifacts.
  • Hypothesis testing with validation: Forms ranked hypotheses, then tests them using logging and targeted minimal tests until the definitive cause is found.
  • Impact and solution strategy: Assesses severity/blast radius, enumerates relevant state space, and recommends the best fix approach with alternatives.

Quick Start

Use the diagnose skill to analyze the bug’s reproduction report and produce a root-cause write-up in artifacts/bugfix/analysis/root-cause.md.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I perform root cause analysis for a software bug?▼

Hypothesis testing for debugging involves forming ranked hypotheses based on reproduction evidence, then validating each through targeted minimal tests and logging until the definitive root cause is confirmed.

How do I trace code paths to find the origin of a regression?▼

Tracing code paths to find a regression involves reviewing historical changes with git blame, mapping the execution flow, and tying the observed failure to concrete artifacts and file:line code references.

What is the best way to document an incident and its root cause?▼

The best way to document an incident is to generate an evidence-based report covering the root cause, impact severity, blast radius, timeline, and file:line references in a structured markdown file.

Why does my bug fix only patch the symptom instead of the real cause?▼

Your bug fix only patches the symptom when you skip systematic root cause analysis, failing to validate ranked hypotheses against reproduction evidence before applying the code correction.

Can I use this diagnosis approach without reproduction evidence?▼

You cannot use this diagnosis approach without reproduction evidence because the root cause analysis requires concrete artifacts, execution flow tracing, and historical change review to validate hypotheses.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
a29paula29paul
1

gstack-openclaw-investigate

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

Community
Advanced
jikig-aijikig-ai
12

git-history-analyzer

Trace code evolution and origins using git log, blame, and shortlog.

Official
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic