skills.rest
schalappe
schalappeCOMMUNITY
Explore all skills by this author →
Website𝕏@HakimKoneGitHub

debugging-strategies

Coordinate systematic evidence gathering, reproduction, and hypothesis validation for debugging software failures.

Updated Aug 23, 2026
Search Tags:#debugging#profiling#regression#git bisect#stack traces#production incidents#differential debugging
One-click install
npx skills add https://github.com/schalappe/skills --skill debugging-strategies-schalappe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-strategies
Source: https://github.com/schalappe/skills/tree/main/debugging-strategies
Command: npx skills add https://github.com/schalappe/skills --skill debugging-strategies-schalappe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you debug elusive failures by turning unclear symptoms into a reproducible, testable problem with evidence-driven narrowing, so you can fix the root cause instead of guessing.

Core Features & Use Cases

  • Reproduce and shrink: Make the bug trigger on demand and reduce it to the smallest failing case, including capturing exact steps and environment details.
  • Gather evidence across layers: Collect error output, environment/runtime versions, deployment timeline changes, and scope (users/regions/data subsets) to clarify where the fault lives.
  • Hypothesize, then test systematically: Apply binary search (or git bisect), differential debugging, and instrumentation to confirm expected vs actual behavior and validate the fix.
  • Use targeted references when needed: Load specialized material for profiling, production-only incidents, language-specific debuggers, and data-layer investigation.
  • Safe production investigation: Follow a strict workflow that prioritizes stabilization and read-only evidence collection, avoiding interactive debugging and risky logging changes on live systems.

Quick Start

Use the debugging-strategies skill when you need to diagnose a production regression by first reproducing the failure off-prod, then applying differential debugging and targeted instrumentation to isolate the single responsible difference.

Frequently Asked Questions about debugging-strategies

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

FAQPage Schema
How do I systematically debug an intermittent production incident?▼

To debug a production incident, follow a strict workflow prioritizing system stabilization and read-only evidence collection, avoiding interactive debugging or risky logging changes on live systems while gathering exact environment details and deployment timeline changes.

How do I use git bisect to track down a regression?▼

Use git bisect to perform a binary search through your commit history, systematically narrowing down the exact code change that introduced the regression by testing working versus broken conditions until you isolate the single responsible difference.

What is differential debugging and when should I use it?▼

Differential debugging compares a working environment against a broken one to isolate the specific variable causing the failure. Use it when you need to confirm expected versus actual behavior across different runtime versions, deployment timelines, or data subsets.

How do I find the root cause of a memory leak from a stack trace?▼

Analyze stack traces to guide your root cause investigation by applying targeted instrumentation and loading specialized references for language-specific debuggers and memory profilers to validate your hypotheses step by step.

What is the best way to reproduce an elusive bug that only happens on demand?▼

Reproduce the elusive bug by capturing exact steps and environment details to trigger it on demand, then shrink the failing case to its smallest form to clarify where the fault lives across application layers and data subsets.

Can I safely collect debugging evidence from a live production database?▼

Yes, you can safely collect production evidence by prioritizing read-only evidence collection and system stabilization, strictly avoiding interactive debugging or risky logging changes that could further impact live users or regions.

Related Skills

Explore More Software Engineering Skills→
haolangehaolange
15

capture-repro

Creates deterministic capture baselines and environment snapshots for runtime debugging.

Community
Advanced
SHUSHU010829SHUSHU010829

spectra-debug

Reproduce, isolate, and confirm root causes with a four-phase debugging workflow.

Community
Advanced
ref-docsref-docs

bug-hunter

Reproduce software bugs, analyze causes, and generate fix plans.

Official
Advanced
davpatel605-beepdavpatel605-beep

systematic-debugging

Identify root causes of software failures through systematic debugging investigation.

Community
Advanced