skills.rest
ramybarsoum
ramybarsoumCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-session

Guide debugging sessions with hypothesis tracking and root cause reports.

Updated Apr 10, 2026
Search Tags:#debugging#investigation#qa#root-cause#incident-response#hypothesis-tracking
One-click install
npx skills add https://github.com/ramybarsoum/RStack-V0 --skill debug-session-ramybarsoum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-session
Source: https://github.com/ramybarsoum/RStack-V0/tree/main/skill/debug-session
Command: npx skills add https://github.com/ramybarsoum/RStack-V0 --skill debug-session-ramybarsoum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging sessions are often unstructured, lose hypotheses, and fail to produce reproducible root-cause documentation; this Skill provides a repeatable, question-driven process to track hypotheses, record investigation steps, and produce a clear root cause summary.

Core Features & Use Cases

  • Hypothesis tracking: Capture, prioritize, and update hypotheses as tests and observations are recorded.
  • Structured investigation log: Guide the user through grouped diagnostic questions, document results, and suggest next steps for reproducing issues.
  • Deliverable output: Produce a concise root cause summary and a saved markdown report suitable for incident follow-up, QA handoff, or PR context.

Quick Start

Start a debug session by describing the bug or pasting the error message and ask for a guided hypothesis-driven investigation.

Frequently Asked Questions about debug-session

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

FAQPage Schema
How do I structure a debugging session to find the root cause of an API error?▼

Yes, hypothesis tracking is an effective debugging technique for intermittent failures because it captures, prioritizes, and updates theories as you record observations and test results. This ensures no potential root cause is lost during the investigation.

What is the best way to document an incident response investigation for a deployment regression?▼

You can start a guided debugging session by pasting the error message or describing the reproducible bug. The process will provide grouped diagnostic questions, suggest next steps for reproduction, and track your investigation log.

Does this hypothesis-driven debugging approach work for intermittent failures across different codebases?▼

The final output of a structured debugging session is a concise root cause summary and a saved markdown report. This deliverable is formatted for saving to work/debug-sessions/[date]-[issue]-debug.md for incident follow-up.

How do I track investigation steps and hypotheses during a QA investigation?▼

A structured debugging session provides a repeatable, question-driven process to track hypotheses and document investigation steps. This prevents losing hypotheses and ensures you produce reproducible root-cause documentation for software issues.

Related Skills

Explore More Software Engineering Skills→
cy-walicy-wali

debug

Guide structured debugging sessions to reproduce, isolate, diagnose, and fix bugs.

Community
Intermediate
kennyolofsson23-netizenkennyolofsson23-netizen

kaizen:analyse-problem

Generate a one-page A3 problem analysis as a structured markdown report.

Community
Intermediate
mattdurhammattdurham
9

error-detective

Analyze logs, traces, and metrics to diagnose root causes across distributed systems.

Community
Advanced
Marwan78888Marwan78888
16

debugging-wizard

Analyze error messages, stack traces, and logs to identify and resolve software issues.

Community
Advanced