debugging
Finds the root cause of failures in any language with a reproduce, hypothesize and prove method, using The Pragmatic Programmer. Use whenever behavior is wrong and the cause is unknown: a stack trace, a bug report, a crash or hang, an intermittent or flaky failure, something broken only in production, a fix that didn't hold, or someone stuck on an error, even if they only paste the message. Covers "por qué falla", "no entiendo este error", "falla a veces", "arreglá este bug" and "en mi máquina anda". Not needed when the cause is already evident from the error; for writing regular tests use testing; to add logging or retries use production-readiness.
Pinned to revision 15e0e74e186c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/debugging/SKILL.md
- skills/debugging/evals/intermittent-cart/case.yaml
- skills/debugging/evals/intermittent-cart/files/cart.py
- skills/debugging/evals/intermittent-cart/files/test_cart.py
- skills/debugging/evals/intermittent-cart/graders/01-critical-root-cause.md
- skills/debugging/evals/intermittent-cart/graders/02-reproduce.md
- skills/debugging/evals/intermittent-cart/graders/03-proof.md
- skills/debugging/evals/intermittent-cart/graders/04-verified.md
- skills/debugging/evals/intermittent-cart/graders/05-tests-intact.md
- skills/debugging/evals/intermittent-cart/graders/06-look-around.md
- skills/debugging/evals/intermittent-cart/prompt.md
- skills/debugging/references/failure-sources.md
- skills/debugging/references/method.md
- skills/debugging/references/production-and-tools.md
Every link opens the file at its source, pinned to the revision this page describes.