dev-debug

Root cause analysis for a software bug involves deriving a slug, creating a debug directory, and outlining 2-5 probable causes with evidence. This skill ranks causes by likelihood and applies a fix to the most probable one after user confirmation.

To debug and fix an issue end to end, provide an issue description to trigger a stepwise protocol. The workflow identifies probable root causes, applies a minimal fix after confirmation, and completes testing, committing, and validation.

The best way to track code fixes and debugging history is using a kept history in a .llm directory. This skill documents root causes, applies fixes, and generates a formal commit message to close the issue and update history.

This debugging workflow relies on version control to complete its end-to-end process. It generates a formal commit message to close the issue and update history, ensuring fixes are properly recorded and validated within your codebase.

Root cause analysis works for any issue description provided as input. The skill requires a concise issue description to begin the debugging workflow, derive a slug, create a debug directory, and outline 2-5 probable causes with evidence.

Confirming the fix before it is applied ensures the correct root cause is targeted. The skill outlines 2-5 probable causes ranked by likelihood with evidence, then waits for user confirmation before applying a minimal fix to the most probable root cause.