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
npx -y skills add ljojua1998/skills --skill debug-findingsAssembled 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
- Collect findings:
- From
$ARGUMENTSif 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.
- From
- 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.
- Each debugger must: reproduce → root-cause → fix → verify (run tests / reproduce
again) → append
finding → root cause → fix → verificationto the ticket's Debug Log (or report it directly if no workboard). - 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).