skills.rest
anortham
anorthamCOMMUNITY
Explore all skills by this author →
GitHub

bug-detective

Diagnose bugs through guided reproduction, tracing, and test-driven verification.

Updated Nov 2, 2025
Search Tags:#debugging#investigation#checkpoint#tests#bug-hunt#trace_call_path
One-click install
npx skills add https://github.com/anortham/mcp-toolbox-workflows --skill bug-detective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-detective
Source: https://github.com/anortham/mcp-toolbox-workflows/tree/main/skills/bug-detective
Command: npx skills add https://github.com/anortham/mcp-toolbox-workflows --skill bug-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables methodical bug investigations using detective-style steps across four phases, combining Sherpa guidance, Julie's tracing tools, and Goldfish’s investigation logging to reproduce, test, fix, and verify bugs.

Core Features & Use Cases

  • 4-phase bug hunt: Reproduce & isolate, capture in test, fix, verify & prevent.
  • Execution tracing: Trace call paths and identify root causes.
  • Investigation logging: Document hypotheses and decisions for future reference.

Quick Start

Tell me about a bug, e.g., "Users see invalid token errors," and I'll lead a four-phase investigation with tests and documented results.

Frequently Asked Questions about bug-detective

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

FAQPage Schema
How do I systematically debug a bug in my codebase?▼

Systematic debugging involves a 4-phase workflow: reproduce and isolate the bug, capture it in a test, apply a fix, then verify and prevent regression. This Skill guides you through each phase with execution tracing and investigation logging to document your findings.

Can I trace call paths to find the root cause of a bug?▼

Yes. Execution tracing tools trace call paths through your code to identify where bugs originate. This Skill combines tracing with guided investigation steps to pinpoint root causes across codebases.

How do I capture a bug in a test before fixing it?▼

Test capture is the second phase of the investigation workflow. You write a test that reproduces the bug, then verify your fix resolves it. This approach ensures the bug stays fixed and prevents future regressions.

What's the best way to document a bug investigation?▼

Investigation logging records your hypotheses and decisions throughout the debugging process. This Skill maintains investigation logs so your reasoning and findings are documented for future reference and team collaboration.

Do I need to know how to write tests to use this debugging workflow?▼

Basic familiarity with writing tests helps, but the Skill guides you through test capture as part of the structured 4-phase approach. The workflow is designed for reproducible bug investigations across codebases of any scale.

Can this approach work for complex bugs across multiple components?▼

Yes. The detective-style workflow applies to bug reports and issue investigations across codebases. Execution tracing and guided reproduction steps help isolate root causes even in complex, multi-component systems.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

bug-report-qa

Generate structured bug reports with reproduction steps and Jira links.

Community
Intermediate
CodeAlive-AICodeAlive-AI
119

bug-fix-protocol

Pair minimal code fixes with failing tests and testing-system audits.

Official
Advanced
dralgorhythmdralgorhythm
111

debugging

Reproduce failures, trace call chains, and isolate root causes in software systems.

Community
Intermediate
thedivergentaithedivergentai
488

godot-debugging-profiling

Debug and profile Godot 4.x projects using breakpoints and profilers.

Community
Intermediate