agentsclimarketplace
Sign in

Debug

Skill panda850819/verbs/skills/engineering/debug

Root-cause route for an observed error, crash, regression, failing test, or intermittent behavior whose cause is still unknown. Reproduce it, name the evidence-backed cause before editing, verify the fix with a red-capable check, and scan for siblings. Use `review` for diff review and `ui` for taste complaints.From its SKILL.md

Install
npx -y skills add panda850819/verbs --skill debug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Debug

You already know how to debug. This skill is not the method. It overrides the momentum reflexes you get wrong and points you to lore you cannot derive.

Override

  • Name the root cause before you edit. At file:function:line, with the evidence. "A state issue" is not a root cause; "stale cache in useUser at user.ts:42, dep array missing userId" is. Editing before you can say that sentence is the failure mode.
  • Diagnosis ends only on a red-capable command. Name one already-run deterministic, fast, agent-runnable command that can fail, and say you saw its output. "I understand the bug" is not done.
  • Do not claim fixed until you ran it and looked. "Should work" is not evidence. Compile-only is not enough for UI / native / generated-artifact bugs: open it, and for generated output read the contents, not the source diff. Cannot run it here → say so and hand off the exact check.
  • Before "fixed", grep the signature for siblings. One fix that ignores siblings leaves N-1 in the tree; the same shape usually hides elsewhere.

Lore (consult when the cause is not obvious)

lib/diagnosis.md — known bug classes (listener-owns-lifetime, O(N²) accumulators, schema category-leak, and CLI archetypes: PATH drift, stdout/stderr contract, pipe backpressure, cold-start), instrument-first-by-bug-class, bisect with worktree safety, and the 3-failed-hypotheses handoff template.

Recall first per @lib/learning-recall.md: pull from the repo learning path configured by the host project, matching the symptom / bug class before hypothesizing. A new reusable bug class emits a candidate using lib/learning-format.md; a match emits a one-line seen again candidate. Never write or update the learning store here. Persistence belongs to the host/project.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.