debug

Reproduce software bugs, gather evidence, trace root causes, and apply minimal fixes.

30|4|Updated Dec 24, 2025

Search Tags:#code quality #testing #debugging #troubleshooting #root cause analysis #bug fixing

Ready to run

npx skills add https://github.com/oursky/skytest-agent --skill debug-oursky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/oursky/skytest-agent/tree/main/skills/development-skills/debug
Command: npx skills add https://github.com/oursky/skytest-agent --skill debug-oursky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, evidence-based approach to debugging software issues, ensuring that bugs are reproduced accurately, root causes are identified, and fixes are minimal and verifiable.

Core Features & Use Cases

Reproduce Issues: Guarantees that a bug can be consistently replicated before any code changes are made.
Evidence Gathering: Collects all necessary logs, error messages, and system states to understand the bug's context.
Root Cause Analysis: Guides the user through tracing the problem's origin across system boundaries.
Minimal Fixes: Ensures that only the necessary code is modified to resolve the bug, preventing unintended side effects.
Failing Tests: Promotes the creation of automated tests to confirm the bug and verify the fix.

Quick Start

Use the debug skill to investigate and fix the reported login error.

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 trace a root cause across service boundaries during debugging?▼

Root cause analysis across service boundaries requires systematically tracing data flow and gathering evidence like logs and system states rather than relying on assumptions. This approach ensures you accurately identify the exact origin of complex software bugs before applying fixes.

How do I systematically reproduce a software bug before attempting a fix?▼

To systematically reproduce a software bug, you must first gather all relevant error messages, logs, and system states. Consistently replicating the issue ensures that the environmental conditions triggering the fault are fully understood before any code changes are made.

Why should I write failing tests when troubleshooting software issues?▼

Writing failing tests during troubleshooting confirms the bug's existence and provides a verifiable baseline for your fix. Once the minimal code modification is applied, the same test validates that the root cause is resolved without introducing regressions.

How do I apply minimal fixes to resolve software bugs without causing side effects?▼

Applying minimal fixes involves modifying only the strictly necessary code identified during root cause analysis. This evidence-based approach prevents unintended side effects by ensuring no unrelated system behavior is altered during the bug resolution process.

Can I use a systematic debugging workflow for handling deprecated code scenarios?▼

Yes, a systematic debugging workflow can handle deprecated code scenarios by tracing data flow and gathering evidence to understand the deprecated logic's impact. This ensures that any minimal fixes applied do not break existing dependencies relying on the old behavior.

What is evidence-based debugging and how does it differ from making assumptions?▼

Evidence-based debugging is the practice of collecting logs, error messages, and system states to understand a bug's context, strictly avoiding assumptions. It ensures that root cause analysis and subsequent minimal fixes are grounded in verified system behavior rather than speculation.