skills.rest
HuynhHoangPhuc
HuynhHoangPhucCOMMUNITY
Explore all skills by this author →
GitHub

sl:debug

Guide structured debugging with evidence-based hypotheses and sl lsp commands.

Updated Mar 12, 2026
Search Tags:#debug#diagnosis#lsp#root-cause#ast#software-debugging
One-click install
npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sl:debug
Source: https://github.com/HuynhHoangPhuc/solon/tree/main/plugins/solon-core/skills/debug
Command: npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a disciplined, evidence-based approach to debugging, ensuring root-cause analysis is performed before any fixes are attempted.

Core Features & Use Cases

  • Collect Symptoms: Gather all available evidence such as LSP diagnostics, logs, and context.
  • Form Hypotheses: Create 2-3 ranked hypotheses grounded in observed data.
  • Test Hypotheses: Trace data flow, verify assumptions, and isolate the smallest reproducible case.
  • Verify Root Cause: Confirm the chain of evidence and ensure all symptoms are explained.
  • Write Diagnosis Report: Produce a reproducible report detailing findings and a recommended non-fix plan.
  • Workflow Integration: Integrates with sl lsp and sl ast commands to drive the debugging lifecycle.

Quick Start

Describe the issue to /sl:debug to initiate a structured root-cause analysis.

Frequently Asked Questions about sl:debug

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

FAQPage Schema
How do I find the root cause of a software bug before applying fixes?▼

To find the root cause of a software bug, gather evidence like LSP diagnostics and logs, form 2-3 ranked hypotheses, trace data flow, and isolate the smallest reproducible case to confirm the chain of evidence.

What is the best way to structure a debugging workflow for unexpected behavior?▼

The best way to structure a debugging workflow for unexpected behavior is an evidence-based process: collect symptoms, test hypotheses by tracing data flow, verify the root cause, and write a reproducible diagnosis report.

How do I use AST and LSP diagnostics to diagnose failures in a codebase?▼

You diagnose failures in a codebase by using AST and LSP diagnostics to collect symptoms, verify assumptions, and trace data flow. This isolates reproducible cases and enforces stepwise testing during root-cause analysis.

Can I use structured debugging for performance issues across a codebase?▼

Yes, you can use structured debugging for performance issues across a codebase. The workflow applies evidence-based hypotheses and stepwise testing to investigate failures, unexpected behavior, and performance degradation.

How do I write a diagnosis report after isolating a reproducible bug?▼

To write a diagnosis report after isolating a reproducible bug, document the confirmed chain of evidence, detail your findings, and provide a recommended non-fix plan to guide subsequent remediation actions.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
zenobi-uszenobi-us
68

sharing-skills

Automate GitHub PR review resolution by fixing comments and failing CI checks.

Official
Intermediate
Agentic-AssetsAgentic-Assets

debugging-wizard

Identify and isolate software root causes through structured reproduction and hypothesis testing.

Official
Advanced
slbugslbug
7

rb:trace

Trace request execution paths in Ruby on Rails, Grape APIs, and Sidekiq jobs.

Community
Intermediate