debugging-patterns
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
Best use case
debugging-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
Teams using debugging-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/debugging-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How debugging-patterns Compares
| Feature / Agent | debugging-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Debugging Patterns ## Overview Provides structured frameworks for root cause analysis. The log-first methodology ensures evidence is gathered before hypotheses are formed. ## Log-First Investigation 1. Read ALL available logs, error output, and stack traces 2. DO NOT form hypotheses before reading evidence 3. Identify the exact error: message, file, line, call stack 4. Determine reproduction steps from evidence 5. Check git log for recent changes correlating with bug introduction ## Pattern-Based Diagnosis - Check patterns.md for known gotchas matching the error - Cross-reference with common patterns: null pointer, race condition, resource leak, config error - Rate root cause confidence (>=80% to proceed with fix) ## Evidence Collection - Stack traces with full call chain - Error messages with context - Exit codes from reproduction attempts - Git blame/log for change correlation - Environment differences (if applicable) ## When to Use - During DEBUG workflow investigation phase - When BUILD tests fail unexpectedly - When reviewing error handling gaps ## Agents Used - `bug-investigator` (primary consumer) - `silent-failure-hunter` (pattern reference)
Related Skills
parallel-patterns
GPU parallel algorithm design patterns and implementations. Implement parallel reduction, scan/prefix sum, histogram, parallel sort algorithms, stream compaction, and work-efficient patterns optimized for specific GPU architectures.
cuda-debugging
Expert skill for GPU debugging using CUDA-GDB and NVIDIA Compute Sanitizer. Detect memory errors, race conditions, uninitialized memory access, validate atomic operations, analyze kernel synchronization issues, and generate debugging reports with recommendations.
fpga-debugging
On-chip debugging skill with ILA, VIO, and related FPGA debug tools
systematic-debugging
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
planning-patterns
Structured planning methodology with research, brainstorming, phased plan creation, risk assessment, and plan-to-build continuity.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
architecture-patterns
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.