debugging

Diagnose software defects with structured debugging and logging strategies.

Updated Jan 24, 2026

Search Tags:#debugging #logging #triage #reproducibility #error-tracing #rubber-duck

Ready to run

npx skills add https://github.com/jaeyeonling/opencode-kit --skill debugging-jaeyeonling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/jaeyeonling/opencode-kit/tree/main/.opencode/skills/debugging
Command: npx skills add https://github.com/jaeyeonling/opencode-kit --skill debugging-jaeyeonling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to debugging, promoting efficient identification and resolution of software defects through predefined strategies, logging best practices, and error tracing techniques.

Core Features & Use Cases

Structured debugging approaches: Scientific debugging, binary search, and rubber duck debugging to isolate root causes.
Logging & error tracing: Best practices for structured logging, contextual data, and cross-module traceability.
Reproducible workflows: Step-by-step processes to reproduce bugs and verify fixes in controlled environments.
Use Case: When debugging a flaky service, apply these methods to quickly locate the offending component and validate the fix.

Quick Start

Start by selecting a failing scenario, enable contextual logging, and follow the structured debugging steps to locate the root cause.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I debug an intermittent failure in a complex asynchronous flow?▼

To debug intermittent asynchronous failures, apply structured debugging strategies like scientific methods and binary search to isolate root causes. Enable contextual logging to trace cross-module interactions and enforce reproducible steps for verifying the fix.

What is the best way to set up logging for error tracing across services?▼

Effective logging for error tracing relies on structured formats and contextual data to ensure cross-module traceability. By implementing robust error context within your logs, you can quickly locate offending components during development, QA, and operations tasks.

How do I reproduce a flaky service bug to verify my fix?▼

Reproducing a flaky service bug requires step-by-step workflows in controlled environments. You establish reproducible steps by enabling contextual logging, applying structured debugging to locate the offending component, and validating the fix against the original failing scenario.

Can I use rubber duck debugging for isolating null errors in development?▼

Yes, rubber duck debugging is a structured approach to isolate null errors by articulating your code logic step-by-step. It helps clarify assumptions and identify root causes quickly when resolving software defects in development and QA contexts.

Does this structured debugging approach apply to operations and production triage?▼

Yes, structured debugging applies directly to operations and production triage. It provides scalable debugging workflows with clear guardrails to diagnose defects, apply error tracing, and resolve intermittent failures across services in live environments.