skills.rest
KodingDev
KodingDevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Identify and resolve root causes of bugs and test failures.

5|Updated Apr 9, 2026
Search Tags:#debug#reproducibility#root-cause#phase-based#software-testing#bug-troubleshooting
One-click install
npx skills add https://github.com/KodingDev/meridian --skill debug-kodingdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/KodingDev/meridian/tree/main/skills/debug
Command: npx skills add https://github.com/KodingDev/meridian --skill debug-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex codebases can be time-consuming and error-prone, often leaving teams with unclear root causes and repeated failures.

Core Features & Use Cases

  • Phase-based root-cause investigation workflow guiding reviewers from error reproduction to verified fixes.
  • Structured evidence gathering, hypothesis tracking, and reproducibility checks to reduce guesswork.
  • Use Case: When a failing test or unexpected exception occurs, apply a repeatable process to isolate the root cause and prevent regressions.

Quick Start

Run the Phase 1 Root Cause Investigation workflow to begin diagnosing the bug.

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 find the root cause of a failing test in a complex codebase?▼

Root-cause debugging uses a structured, phase-based workflow to investigate failing tests, requiring reviewers to reproduce the error, gather evidence, and confirm hypotheses before applying fixes to eliminate guesswork and prevent regressions.

How do I troubleshoot unexpected exceptions without relying on guesswork?▼

Troubleshoot unexpected exceptions by entering a phase-based investigation workflow that tracks hypotheses and enforces reproducibility checks, ensuring you only implement code fixes after strictly confirming the root cause of the bug.

Why does my software bug keep reappearing after applying a patch?▼

Bugs reappear when patches address symptoms rather than the root cause; a disciplined debugging workflow forces you to gather evidence and verify reproducibility before implementing fixes, thereby preventing repeated failures and regressions.

How do I start a root-cause investigation when a bug occurs?▼

Start a root-cause investigation by running the Phase 1 workflow to identify the issue scope and reproduce the error, progressing through subsequent phases to analyze evidence and implement verified fixes only after confirmation.

What is the purpose of reproducibility checks in software bug troubleshooting?▼

Reproducibility checks in bug troubleshooting validate that the identified root cause consistently triggers the failure, ensuring the subsequent fix actually resolves the original issue and preventing future code regressions.

Related Skills

Explore More Software Engineering Skills→
KingInYellowsKingInYellows

ce-debug

Diagnose bugs through a phase-based investigation from symptom to root cause.

Official
Advanced
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate
D0NMEGAD0NMEGA
8

gsd-list-phase-assumptions

Identify Claude's assumptions about a project phase before planning.

Community
Intermediate
anishs1207anishs1207
1

canary

Monitor live URLs with the browse daemon and visual baselines to detect post-deploy failures.

Community
Advanced