skills.rest
ambient-code
ambient-codeOFFICIAL
Explore all skills by this author →
GitHub

diagnose

Analyze reproduction data and code paths to identify root causes of bugs.

3|38|Updated Nov 6, 2025
Search Tags:#debugging#reproduction#root-cause-analysis#git-blame#code-paths#hypothesis-testing
One-click install
npx skills add https://github.com/ambient-code/workflows --skill diagnose-ambient-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/ambient-code/workflows/tree/main/workflows/bugfix/.claude/skills/diagnose
Command: npx skills add https://github.com/ambient-code/workflows --skill diagnose-ambient-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic root-cause analysis to identify the underlying issue causing a bug, not just surface symptoms.

Core Features & Use Cases

  • Guided, stepwise investigation starting from reproduction data through code-path tracing.
  • Hypothesis formation and testing with evidence collection and git history review.
  • Impact assessment across modules to determine blast radius and fix strategy.
  • Use Case: An intermittent defect that only appears under specific conditions can be traced to a failing edge case in a shared utility.

Quick Start

Review the reproduction data, map failure points to code paths, and iteratively test hypotheses to identify the root cause.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is the best way to perform root-cause analysis for intermittent bugs?▼

Root-cause analysis for intermittent bugs requires systematically reviewing reproduction data, mapping failure points to code paths, and iteratively testing hypotheses to identify underlying issues rather than surface symptoms.

How do I trace code paths from reproduction data to find a defect?▼

To trace code paths from reproduction data, map the specific failure conditions to the affected code paths, review git history for historical changes, and collect structured evidence to test your hypotheses.

How does git blame help with hypothesis testing during debugging?▼

Git blame supports hypothesis testing during debugging by providing historical change references, allowing you to trace when specific code paths were modified and correlate those changes with the emergence of the defect.

Can I assess the blast radius of a bug across multiple modules?▼

Yes, you can assess the blast radius of a bug by analyzing impact across modules to determine the extent of the defect and formulate a durable fix strategy based on the documented findings.

When do I need structured evidence collection for debugging?▼

Structured evidence collection for debugging is needed when investigating complex defects that require traceable references, ensuring that hypothesis testing and documented findings support durable fixes across repositories.

Related Skills

Explore More Software Engineering Skills→
karithamkaritham
2

debugging

Document failure evidence and isolate root causes with hypothesis testing.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
I194I194
9

canary

Monitor deployed apps for console errors, performance regressions, and page failures.

Community
Advanced