agentsclimarketplace

Debug findings

Skill ljojua1998/skills/.claude/skills/debug-findings

Run the debugger agent over open findings (from /qa, /security-audit, the workboard, or a pasted bug report) — root-cause, fix, verify, and re-check. Use when the user asks to fix reported bugs/findings.From its SKILL.md

Install
npx -y skills add ljojua1998/skills --skill debug-findings

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

1.1 KB, as published. Nobody here has run it

/debug-findings — Fix Open Findings

  1. Collect findings:
    • From $ARGUMENTS if the user pasted/described them.
    • Else from workboard/tickets/* — all unresolved entries in QA/Security/Audit findings sections (a finding is resolved when the Debug Log references it).
    • Else from the last QA/security report in this conversation.
  2. Group findings by area/file. Spawn the debugger agent per independent group (in parallel) with: the findings, relevant ticket paths, and how to run tests.
  3. Each debugger must: reproduce → root-cause → fix → verify (run tests / reproduce again) → append finding → root cause → fix → verification to the ticket's Debug Log (or report it directly if no workboard).
  4. After fixes, re-run the relevant reviewer agent scoped to the fixed areas to confirm resolution (one re-check round; report anything still open honestly).

Keep looking

Skills are one crate of 610,220. 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.