skills.rest
sacharavya
sacharavyaCOMMUNITY
Explore all skills by this author →
GitHub

debug-detective

Diagnose codebase bugs by analyzing error messages, stack traces, and logs.

Updated Aug 27, 2026
Search Tags:#debugging#troubleshooting#triage#root-cause-analysis#log-analysis#error-trace
One-click install
npx skills add https://github.com/sacharavya/b-b-i-crm --skill debug-detective-sacharavya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-detective
Source: https://github.com/sacharavya/b-b-i-crm/tree/main/.claude/skills/debug-detective
Command: npx skills add https://github.com/sacharavya/b-b-i-crm --skill debug-detective-sacharavya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically diagnosing bugs, errors, and unexpected behaviour in codebases by analyzing error messages, stack traces, and log output. It helps when users say it's not working, there is an error, or a crash, enabling a targeted path from symptom to root cause.

Core Features & Use Cases

  • Triages evidence from error messages, stack traces, and logs to identify the root cause.
  • Generates structured hypotheses and guides focused debugging steps.
  • Suitable for development, testing, and maintenance workflows to reduce mean time to resolution.

Quick Start

Paste the full error message and stack trace, or describe the failure, and I will start a guided debugging session.

Frequently Asked Questions about debug-detective

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

FAQPage Schema
How do I diagnose a bug from a stack trace and error message?▼

To diagnose a bug from a stack trace, paste the full error message and trace output to initiate a structured triage workflow that formulates hypotheses and identifies the root cause of the failure.

What is the best way to perform root cause analysis on application logs?▼

Root cause analysis on application logs is performed by triaging log output to generate structured hypotheses, testing potential fixes, and documenting the outcome to systematically reduce mean time to repair.

How do I troubleshoot unexpected code crashes during testing?▼

Troubleshoot unexpected code crashes during testing by applying a structured investigative workflow that analyzes error traces, formulates targeted hypotheses, and guides focused debugging steps to isolate the failure.

Can I use this triage workflow for general software maintenance?▼

Yes, you can use this triage workflow for general software maintenance as it systematically diagnoses unexpected behavior in codebases across development, testing, and troubleshooting scenarios to reduce repair time.

What do I need to start debugging an error trace?▼

To start debugging an error trace, you need to provide the full error message and stack trace, or simply describe the failure, to trigger a guided investigative session that isolates the root cause.

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
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
chagongchagong
1

find-duplicates

Identify duplicate GitHub issues using semantic similarity and confidence scoring.

Community
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

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

Official
Basic