skills.rest
Qualiasolutions
QualiasolutionsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qualia-debug

Diagnose software bugs through stepwise symptom gathering and verified fixes.

Updated Aug 23, 2026
Search Tags:#git#performance#debugging#troubleshooting#frontend#diagnosis#root-cause
One-click install
npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qualia-debug
Source: https://github.com/Qualiasolutions/qualia-framework/tree/main/skills/qualia-debug
Command: npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable debugging workflow so engineers can gather accurate symptoms, confirm diagnoses with users, and apply minimal verified fixes rather than guessing.

Core Features & Use Cases

  • Symptom gathering: Guided questions to capture exact errors, expected behavior, start time, and attempts made.
  • Diagnosis confirmation: Present a clear diagnosis before any code changes and wait for user confirmation to avoid incorrect fixes.
  • Investigate, isolate, and fix: Stepwise reproduction, binary search isolation, root-cause identification, minimal patching, verification, and commit.
  • Modes: Interactive mode for general debugging, frontend mode for CSS/layout issues, and perf mode for profiling and hot-path optimization.
  • Use Cases: Fixing a layout overflow in a web app, tracking down a backend exception, or diagnosing a slow page load and applying targeted performance improvements.

Quick Start

Use the qualia-debug skill interactively by describing the observed error, the expected behavior, what you have tried, and which mode (frontend or perf) to use.

Frequently Asked Questions about qualia-debug

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

FAQPage Schema
What is the best way to systematically debug a software bug instead of guessing?▼

Systematic debugging requires a structured workflow that gathers exact symptoms, confirms a diagnosis before altering code, and isolates the root cause. This approach ensures minimal verified fixes are applied and committed rather than relying on trial-and-error patches.

How do I fix a frontend CSS layout overflow without breaking existing styles?▼

Fix a frontend CSS layout overflow using a guided debugging mode tailored for web layouts. It helps reproduce the visual issue, isolate the problematic style rules, and apply a minimal verified patch to resolve the overflow without disrupting the broader stylesheet architecture.

How do I find the root cause of a performance bottleneck in a web application?▼

Find a performance bottleneck by running a profiling mode that investigates hot-paths and slow page loads. This process isolates the exact backend or frontend operations causing latency, allowing you to apply targeted performance improvements and verify the optimization.

Can I diagnose a backend exception step by step before making any code changes?▼

Yes, you can diagnose a backend exception through interactive symptom gathering and binary search isolation. The workflow requires you to present a clear root-cause diagnosis and wait for confirmation before applying any code changes, preventing incorrect fixes.

Why should I confirm a software diagnosis before applying a patch?▼

Confirming a software diagnosis before patching prevents incorrect fixes and unnecessary code changes. By validating the isolated root cause against gathered symptoms, you ensure that only a minimal, verified fix is committed to the repository.

What do I need to start a troubleshooting session for a slow web page load?▼

To start troubleshooting a slow web page load, you need to describe the observed error, the expected behavior, previous attempts made, and specify performance mode. This input drives the profiling investigation to isolate and optimize the identified hot-paths.

Related Skills

Explore More Software Engineering Skills→
anderssonqanderssonq
1

nvsinner-debugging-playbook

Diagnose NvSinner configuration failures by mapping symptoms to verified fixes.

Community
Advanced
bjornjeebjornjee
19

fix

Reproduce a software defect in an isolated git worktree, then validate a minimal fix with tests.

Community
Advanced
softmgsoftmg

Pair Programming

Coordinate role-based pair programming sessions with automated testing and verification.

Official
Advanced
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

debugging-systematic

Apply hypothesis-driven analysis and binary search to isolate software bugs.

Official
Intermediate