Loading...
Loading...
Found 65 Skills
Implement and run measurements that settle hypotheses before making implementation or fixes, and make decisions based only on the results. Use when investigating the cause of a defect, comparing performance or behavior, starting a new feature, or whenever you are about to judge something with “probably.”
Systematic debugging discipline based on David Agans' nine rules, understand the system, reproduce reliably, bisect the search space, change one variable at a time, keep an audit trail, and never declare a fix done until it's verified against the original failure. Use when the user reports something broken, throwing, failing, or slow, or says "diagnose" / "debug this".
Fixes a bug by building a runnable reproduction and finding the root cause before any fix. Use for errors, crashes, failing tests or builds, flaky behavior, or repeated failed fixes.
Break out of a repeating failure: name the assumption behind all the failed fixes, test it directly, list three other approaches, pick one, and restart clean if needed. Use when the same error or wrong behavior comes back after two fix attempts, or when you notice you are retrying small variations. Invoke as /ds-unstick.
Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then fix and show before/after.