A systematic debugging process that prioritizes evidence-based root-cause analysis over speculative fixes.

Install

mkdir -p .claude/skills/investigate-yokoyamaryota && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15003" && unzip -o skill.zip -d .claude/skills/investigate-yokoyamaryota && rm skill.zip

Installs to .claude/skills/investigate-yokoyamaryota

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Root-cause-first debugging workflow. Use for bugs, regressions, stack traces, production issues, or any case where the real failure path must be understood before edits are proposed.
182 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Reproduce the issue and capture exact symptoms
  • Trace the real execution path
  • Form the smallest plausible root-cause hypothesis
  • Verify the hypothesis against code or runtime evidence
  • Propose or implement a fix

How it works

This skill defines a sequential workflow that starts with reproducing an issue and ends with verifying a hypothesis before proposing a fix.

Inputs & outputs

You give it
A bug, regression, stack trace, or production issue
You get back
A verified root-cause hypothesis and a proposed fix

When to use investigate

  • Debugging production issues
  • Investigating regressions
  • Analyzing stack traces
  • Root cause analysis
  • Verifying bug fixes

About this skill

Investigate

Rules

  • no speculative fixes
  • gather evidence before changing code
  • separate observations, hypotheses, and fixes

Workflow

  1. Reproduce the issue and capture exact symptoms.
  2. Trace the real execution path.
  3. Form the smallest plausible root-cause hypothesis.
  4. Verify the hypothesis against code or runtime evidence.
  5. Only then propose or implement a fix.

When not to use it

  • When a speculative fix is desired
  • When code changes are preferred before gathering evidence
  • When observations, hypotheses, and fixes are not separated

Limitations

  • This skill does not permit speculative fixes
  • This skill requires evidence gathering before code changes
  • This skill separates observations, hypotheses, and fixes

How it compares

This workflow enforces a structured, evidence-based approach to debugging, unlike directly attempting fixes.

Compared to similar skills

investigate side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
investigate (this skill)04moNo flagsIntermediate
corpus-management02moReviewAdvanced
python-testing-patterns772moReviewIntermediate
chrome-devtools417moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry