skills.rest
drimchansky
drimchanskyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Guide systematic reproduction, isolation, diagnosis, and verification of software bugs.

Updated Feb 8, 2026
Search Tags:#code quality#testing#debugging#troubleshooting#software development#bug fixing
One-click install
npx skills add https://github.com/drimchansky/agents-kit --skill debug-drimchansky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/drimchansky/agents-kit/tree/main/skills/debug
Command: npx skills add https://github.com/drimchansky/agents-kit --skill debug-drimchansky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured methodology to systematically investigate, diagnose, and resolve software bugs, ensuring that fixes are effective and verified.

Core Features & Use Cases

  • Reproduce Bugs: Confirms the existence and observability of a bug before attempting a fix.
  • Isolate Issues: Narrows down the problem area using techniques like tracing data flow and bisection.
  • Diagnose Root Cause: Identifies the fundamental reason for the bug, not just the symptom.
  • Implement & Verify Fixes: Applies targeted changes and confirms resolution with tests.
  • Use Case: When a user reports a critical UI glitch, this skill guides the developer through reproducing the issue, pinpointing the faulty component, understanding why it fails, applying the minimal fix, and verifying that the glitch is gone and no new issues were introduced.

Quick Start

Use the debug skill to investigate the reported login failure.

Frequently Asked Questions about debug

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

FAQPage Schema
What is the best way to systematically fix software bugs instead of guessing?▼

To systematically fix software bugs, you should follow a structured process to reproduce, isolate, diagnose, and fix the issue. This approach emphasizes understanding the root cause before applying changes and verifying the resolution through testing.

How do I isolate a bug when tracing data flow in my code?▼

To isolate a bug during data flow tracing, narrow down the problem area using bisection techniques. This helps pinpoint the faulty component by systematically eliminating parts of the code that function correctly.

How do I diagnose the root cause of a critical UI glitch?▼

To diagnose the root cause of a critical UI glitch, first reproduce the issue to confirm its observability, then trace the data flow to pinpoint the failing component, ensuring you identify the fundamental reason rather than just the symptom.

How do I verify a bug fix against edge cases after implementing a change?▼

To verify a bug fix against edge cases, apply targeted changes and confirm the resolution by running tests. This ensures the original glitch is gone and no new issues were introduced during troubleshooting.

Why should I reproduce a bug before attempting a software fix?▼

You should reproduce a bug before attempting a software fix to confirm the existence and observability of the issue. This step ensures you are addressing an actual defect rather than an unconfirmed report.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
240

bug-reproduction-validator

Reproduce and validate bug reports to classify issues as confirmed bugs.

Official
Advanced
apokamoapokamo
12

issue-verify-code

Verify code fixes against prior feedback and git diff HEAD~1.

Community
Intermediate
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate
StrategicMilkStrategicMilk

Monitoring and Alerting

Detect operational anomalies in system metrics using statistical process control.

Community
Advanced