skills.rest
Sh3rd3n
Sh3rd3nCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Guide systematic four-phase debugging with adaptive techniques for issue types.

3|Updated Feb 19, 2026
Search Tags:#code quality#testing#troubleshooting#root cause analysis#bug fixing#debug
One-click install
npx skills add https://github.com/Sh3rd3n/megazord --skill debug-sh3rd3n
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Sh3rd3n/megazord/tree/main/skills/debug
Command: npx skills add https://github.com/Sh3rd3n/megazord --skill debug-sh3rd3n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, step-by-step approach to identify and resolve bugs in code, ensuring thoroughness and clarity.

Core Features & Use Cases

  • Systematic Debugging: Guides users through four distinct phases: Reproduce, Isolate, Root Cause, and Fix.
  • Adaptive Techniques: Adjusts debugging strategies based on the type of issue (runtime error, build failure, etc.).
  • Use Case: When encountering an unexpected runtime error, this Skill will help you reliably reproduce the error, pinpoint the exact code causing it, understand the underlying reason, and implement a verified fix.

Quick Start

Use the debug skill to fix the runtime error in the attached file 'app.js'.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a runtime error systematically?▼

To debug a runtime error systematically, follow four phases: reproduce, isolate, root cause, and fix. This process ensures thorough bug fixing by adapting troubleshooting techniques based on the specific issue type.

What is the best way to find the root cause of a build failure?▼

Finding the root cause of a build failure requires isolating the exact configuration or code causing the error. Systematic debugging techniques adapt to build failures, helping pinpoint the underlying reason and implement a verified fix.

How do I troubleshoot a test failure in my code?▼

Troubleshooting a test failure involves isolating the failing test and identifying the root cause. Systematic debugging adapts strategies for test failures, guiding you through reproducing the issue and applying a targeted fix.

Can I use quick debugging for logic bugs instead of a full systematic approach?▼

Yes, you can use quick debugging for logic bugs by configuring the mode. The Skill supports both systematic four-phase debugging and quick debug modes, allowing you to choose the depth of troubleshooting based on your needs.

Does systematic debugging work for performance issues?▼

Yes, systematic debugging works for performance issues by adapting techniques to the issue type. It guides you through reproducing the performance bottleneck, isolating the code, finding the root cause, and applying a fix.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
adobeadobe
45

Testing Blocks

Validate Alpine Eco Drive project code changes with unit, browser, linting and performance checks.

Official
Intermediate
WomenDefiningAIWomenDefiningAI
9

ui-ux-audit

Audit existing UI/UX source files to detect duplication before implementing changes.

Official
Advanced
xotongxotong

investigate

Trace root causes in failing software through a structured four-phase investigation workflow.

Community
Advanced