skills.rest
jeanluciano
jeanlucianoCOMMUNITY
Explore all skills by this author →
GitHub

Debugging Issues

Diagnose software bugs through systematic reproduction, isolation, and hypothesis testing.

20|2|Updated Jul 8, 2025
Search Tags:#debugging#hypothesis#root-cause#reproduction#log-analysis#incident
One-click install
npx skills add https://github.com/jeanluciano/quaestor --skill debugging-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debugging Issues
Source: https://github.com/jeanluciano/quaestor/tree/main/src/quaestor/skills/debugging-issues
Command: npx skills add https://github.com/jeanluciano/quaestor --skill debugging-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured, repeatable debugging workflows to reproduce issues, analyze errors, test hypotheses, and implement fixes efficiently.

Core Features & Use Cases

  • Reproduction steps capture: document exact steps to reliably reproduce a bug
  • Systematic isolation: techniques to narrow down the fault domain
  • Log and error analysis: collect and interpret messages, traces, and patterns
  • Hypothesis testing: frame theory, test predictions, and iterate
  • Production incident response: structured playbook for triage and remediation

Quick Start

Provide a reproducible bug report by listing steps to reproduce, expected vs actual behavior, environment details, and any relevant logs.

Frequently Asked Questions about Debugging Issues

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

FAQPage Schema
How do I reproduce a bug systematically to identify the root cause?▼

Reproduce bugs by documenting exact steps, environment details, expected versus actual behavior, and relevant logs. Systematic reproduction isolates the fault domain and enables hypothesis testing to identify root cause.

What's the best way to analyze logs and error messages when debugging?▼

Collect logs and error traces, interpret patterns and messages to pinpoint failure points. Log analysis reveals timing, state transitions, and anomalies that form the basis for structured hypothesis testing.

How do I test debugging hypotheses and verify fixes work?▼

Frame theory based on evidence, test predictions against reproduced steps, iterate with new data. Verify outcomes by re-running reproduction steps and confirming expected behavior after implementing fixes.

Can I use structured debugging workflows for production incidents?▼

Yes. Production incident response applies the same systematic approach: triage via reproduction, isolate causes through log analysis, test hypotheses, and verify remediation across development, staging, and production environments.

What should I document when capturing bug reproduction steps?▼

Document exact steps to reliably reproduce the bug, environment configuration, expected behavior, actual behavior, and relevant logs or error traces. Complete reproduction documentation enables efficient hypothesis testing and fix verification.

Related Skills

Explore More Software Engineering Skills→
csackridercsackrider

report-bug

Collect environment details and errors into a structured bug report.

Community
Intermediate
alexchloualexchlou
2

matter-close

Record legal matter closures with resolution details, costs, and lessons.

Community
Intermediate
koralliskorallis
90

monitoring-observability

Implement monitoring, logging, metrics, and tracing with Grafana and Sentry.

Community
Intermediate
mvillmowmvillmow
18

analyze-ci-failure-logs

Analyze CI failure logs to identify root causes and error patterns.

Community
Intermediate