debugging

Guide root-cause isolation for TypeScript/Next.js, Go, Python, and C# bugs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ashwnn/agent-config --skill debugging-ashwnn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/ashwnn/agent-config/tree/main/skills/debugging
Command: npx skills add https://github.com/ashwnn/agent-config --skill debugging-ashwnn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured debugging workflow with stack-specific techniques for TypeScript/Next.js, Go, Python, and C#. Covers deterministic and intermittent bugs, async issues, and systematic root-cause isolation.

Core Features & Use Cases

  • Universal Protocol: reproduction, bisecting, hypothesis, fixes, verification.
  • Stack-Specific Techniques: TypeScript/Next.js, Go, Python, C# debugging patterns.
  • Intermittent Bug Protocol: structured logging, correlation IDs, controlled reproduction.

Quick Start

Run the debugging workflow on a failing project by documenting a reproducible bug, reproducing it deterministically, and applying the universal protocol to isolate 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 systematically debug a reproducible bug across different programming stacks?

Systematic debugging across stacks uses a universal protocol: reproducing the bug deterministically, bisecting to isolate the root cause, forming a hypothesis, applying a fix, and verifying the resolution. This structured workflow ensures safe, verifiable resolution across TypeScript, Go, Python, and C#.

What is the best way to isolate the root cause of an intermittent bug?

To isolate an intermittent bug root cause, apply a structured intermittent bugs protocol utilizing structured logging, correlation IDs, and controlled reproduction. This isolates elusive async issues and cross-stack scenarios by forcing deterministic behavior from inconsistent failures.

Does this debugging workflow support Python and C# async issues?

Yes, this debugging workflow supports Python and C# async issues by applying stack-specific techniques alongside the universal protocol. It handles both deterministic and intermittent async failures, guiding root-cause isolation for these specific programming environments.

How do I fix a failing TypeScript or Next.js project using a structured debugging process?

Fixing a failing TypeScript or Next.js project involves documenting a reproducible bug, reproducing it deterministically, and applying the universal protocol. Stack-specific techniques isolate the root cause, followed by a structured fix-and-verify checklist to ensure safe resolution.

Why should I use a universal debugging protocol instead of ad-hoc troubleshooting?

A universal debugging protocol provides a reproducible reproduction protocol, a bisect-and-hypothesis process, and a structured fix-and-verify checklist. Unlike ad-hoc troubleshooting, this systematic root-cause isolation ensures verifiable resolution across deterministic, intermittent, and cross-stack bugs.