Debug

by cyrusagents9cb20212dfb0caec7fc44a4688d41829589087bcNo license850 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.

AI-generated overview

Guides a structured debugging workflow: reproduce a bug, find its root cause, then apply a minimal verified fix.

What it does: This skill provides a two-phase debugging procedure for a reported issue. Phase one investigates the bug report, traces the symptom to its source, identifies the root cause, reproduces the error with the smallest useful check, and documents the cause and reproduction steps. Phase two plans and implements a minimal targeted fix, then repeats the reproduction and runs relevant existing checks to verify it.
When to use it: Use it when a specific bug has been reported and needs to be diagnosed and fixed. It suits situations where the cause is unknown and a disciplined reproduce-then-fix approach is wanted, rather than broad refactoring or unrelated improvements.
Requirements: No scripts or special tooling are required; it is an instructions-only workflow. It assumes access to the codebase and the ability to run commands or tests to reproduce the issue.

Debug a reported issue using a structured reproduction-then-fix approach.

Investigate — Analyze the bug report for key symptoms and error messages
Trace — Search the codebase for error occurrence patterns, trace from symptom to source
Root cause — Identify the root cause through data flow analysis and edge case checking
Reproduce — Reproduce the exact error with the smallest useful check (a command, dry run, manual flow, or automated test)
Document — Clearly document the root cause and reproduction steps

Plan — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase
Implement — Make the minimal, targeted fix that addresses the root cause
Verify — Repeat the reproduction to confirm the fix and run relevant existing checks. Follow verify-and-ship for proportionate scope; add a regression test only when the concrete failure warrants durable coverage

Minimal changes — Fix the bug, nothing more
Targeted — Only touch affected code paths
Verified — Confirm the reproduction succeeds after the fix and preserve relevant existing safeguards; a new test file is not mandatory
No unrelated improvements — Stay focused on the specific bug

Source and attribution

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.