skills.rest
aubrian-halili
aubrian-haliliCOMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose and fix code bugs using a reproduce-isolate-hypothesize-fix-verify methodology.

Updated Feb 13, 2026
Search Tags:#code quality#testing#debugging#troubleshooting#error handling#bug fixing
One-click install
npx skills add https://github.com/aubrian-halili/ai-experience --skill debug-aubrian-halili
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/aubrian-halili/ai-experience/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/aubrian-halili/ai-experience --skill debug-aubrian-halili

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically diagnose and fix bugs, errors, or failing tests in your code, ensuring a clear path to resolution.

Core Features & Use Cases

  • Reproduce & Isolate: Guarantees bugs are reproduced before fixing and narrows down the issue to the smallest code segment.
  • Hypothesize & Fix: Guides you through forming and testing single hypotheses for the root cause, applying minimal fixes.
  • Verify: Ensures fixes are validated and do not introduce regressions.
  • Use Case: You're encountering a TypeError in your application. Use this Skill to trace the error back to its source, identify the faulty logic, and apply the correct fix.

Quick Start

Use the debug skill to fix the failing test 'user-auth.test.ts'.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I systematically debug a TypeError in my code?▼

To debug a TypeError systematically, you reproduce the error, isolate the faulty code segment, hypothesize the root cause, apply a minimal fix, and verify the result to prevent regressions.

What is the best way to troubleshoot failing tests and fix bugs without introducing regressions?▼

The best way to troubleshoot failing tests is using an evidence-based methodology that forms single hypotheses, applies minimal fixes, and validates the code to ensure fixes do not introduce regressions.

Can I use a structured debugging methodology to isolate errors from stack traces?▼

Yes, you can use a structured debugging methodology to process stack traces by isolating the issue to the smallest code segment before forming a hypothesis and applying a fix.

Does systematic bug fixing work for handling scope creep and analysis paralysis?▼

Yes, systematic bug fixing handles scope creep and analysis paralysis through built-in guards that enforce forming single hypotheses, applying minimal fixes, and verifying results without over-analyzing.

How to trace an error back to its source and apply a minimal fix?▼

To trace an error to its source, you reproduce the bug, isolate it to the smallest code segment, hypothesize the root cause, and apply a minimal fix to resolve the faulty logic.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
sumilee-pcusumilee-pcu

regression-suite

Map GDD critical paths and closed bugs to existing test suites.

Community
Advanced
guccangguccang
3

requesting-code-review

Automate pre-commit code review for security issues, regressions, and quality problems.

Community
Advanced
SethyPagnaSethyPagna

python-debugpy

Attach interactive debuggers to Python processes for breakpoint-driven tracing.

Community
Advanced