skills.rest
stackrox
stackroxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

diagnose

Trace code execution and git history to produce evidence-based root-cause reports.

Updated Aug 27, 2026
Search Tags:#debugging#reporting#code-review#analyze#root-cause#bug#git-blame
One-click install
npx skills add https://github.com/stackrox/ambient-workflows --skill diagnose-stackrox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/stackrox/ambient-workflows/tree/main/workflows/bugfix/.claude/skills/diagnose
Command: npx skills add https://github.com/stackrox/ambient-workflows --skill diagnose-stackrox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform thorough root-cause analysis to identify why a bug occurs, focusing on underlying causes and evidence-based reasoning rather than superficial symptoms.

Core Features & Use Cases

  • Structured Analysis: guides the user from reproduction review through hypothesis testing to a documented root-cause report.
  • Evidence-based Conclusions: emphasizes traceable reasoning with code references and logs.
  • End-to-end Debug Workflow: applicable to code paths, data failures, and historical changes across the codebase.

Quick Start

Review a failing scenario, trace the entry point, and produce a concise root-cause report.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is root-cause analysis in software debugging and when do I need it?▼

Root-cause analysis identifies the underlying cause of a bug rather than superficial symptoms. You need it when resolving complex code path failures, data issues, or historical changes that require evidence-based conclusions to inform permanent fixes.

How do I perform root-cause analysis using git blame and reproduction data?▼

Perform root-cause analysis by reviewing reproduction data, tracing code execution from the entry point, and using git blame to inspect historical changes. Form hypotheses, test them with targeted logging, and document a comprehensive root-cause report with evidence.

What's the best way to trace code execution to find the underlying cause of a bug?▼

The best way to trace code execution for a bug is following a structured analysis process: review reproduction data, trace the entry point, use git blame for historical changes, form hypotheses, test them with targeted logging, and document evidence-based conclusions.

Can I use structured root-cause analysis for data failures and historical code changes?▼

Yes, structured root-cause analysis applies to data failures and historical code changes. It guides you through reviewing reproduction data, tracing code paths, using git blame to inspect changes, and testing hypotheses to produce evidence-based conclusions for fixes.

How do I document a comprehensive root-cause report after debugging?▼

Document a comprehensive root-cause report by compiling traceable evidence gathered during debugging. Include code references, targeted logs, tested hypotheses, and historical git blame data to produce evidence-based conclusions that directly inform the software fix.

Related Skills

Explore More Software Engineering Skills→
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
xloxn69xloxn69
7

agileflow-story-writer

Convert feature descriptions into structured user stories with acceptance criteria.

Community
Intermediate
theinternetitheinterneti

gitnexus-exploring

Index, query, and analyze execution flows and symbol contexts in codebases.

Community
Intermediate
him55710-sudohim55710-sudo

investigate

Identify bug root causes using a four-phase investigation workflow.

Community
Advanced