skills.rest
SeifBenayed
SeifBenayedCOMMUNITY
Explore all skills by this author →
GitHub

debug

Trace root causes of application errors and test failures using stack traces and git history.

114|31|Updated Mar 23, 2026
Search Tags:#troubleshooting#root cause analysis#debug#error resolution#code investigation#test failure
One-click install
npx skills add https://github.com/SeifBenayed/cloclo --skill debug-seifbenayed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/SeifBenayed/cloclo/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/SeifBenayed/cloclo --skill debug-seifbenayed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming, frustrating process of manually tracing the root cause of errors, test failures, and unexpected application behavior, letting you quickly identify and resolve issues without guesswork.

Core Features & Use Cases

  • Systematic Issue Diagnosis: Follows a structured 5-step workflow to understand, reproduce, investigate, verify hypotheses, and report root causes for any reported error or unexpected behavior.
  • Targeted Code Investigation: Uses stack traces, error messages, and git history to pinpoint the exact source of issues, checking for common problems like missing dependencies, type mismatches, race conditions, and environment misconfigurations.
  • Use Case: If your test suite is failing with a cryptic stack trace after a recent code change, use this Skill to automatically trace the error to the exact line of code, identify the root cause (like a missing null check), and get a clear explanation of how to fix it.

Quick Start

Use the debug skill to investigate the recent test failure in the user authentication module and explain the root cause and suggested fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I trace the root cause of a runtime crash using a stack trace?▼

To trace the root cause of a runtime crash, you analyze the stack trace and error messages against your source code. This skill systematically investigates the execution context and git history to pinpoint the exact failing line and identify the underlying issue.

Why does my test suite fail with a cryptic error after a recent code change?▼

A failing test suite after a code change often indicates a broken dependency, type mismatch, or missing null check. By checking git history and reproducing the test failure, you can verify hypotheses and isolate the exact code modification responsible.

What's the best way to diagnose unexplained behavior changes in my application post-deployment?▼

The best way to diagnose unexplained post-deployment behavior changes is systematic root cause analysis. This involves reproducing the unexpected behavior, investigating execution context, and verifying hypotheses against recent code modifications without making unrequested changes.

Do I need access to git history to investigate the root cause of an error?▼

Yes, you need access to git history to investigate the root cause of an error effectively. Reviewing recent code modifications alongside error messages and stack traces allows you to trace broken behavior back to the specific source code changes that introduced the issue.

Can I use this approach to fix race conditions and environment misconfigurations?▼

Yes, you can use this systematic investigation approach to fix race conditions and environment misconfigurations. By analyzing error messages and execution context, the workflow targets common problems like missing dependencies and type mismatches to report the root cause.

Related Skills

Explore More Software Engineering Skills→
ps-carvalhops-carvalho

debug

Analyze logs, stack traces, and git history to identify software defect root causes.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

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

Community
Advanced
erenisiklarerenisiklar

address-sanitizer

Detect memory errors in C/C++ fuzzing with AddressSanitizer.

Community
Advanced
519lab519lab
2

python-debugpy

Provides interactive and remote debugging for Python applications via pdb and debugpy.

Official
Advanced