Investigate unknown defects by forming hypotheses and gathering cited evidence.
npx skills add https://github.com/arbiterForge/codeArbiter --skill debug-arbiterforge
Please help me install this Agent Skill. Skill: debug Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/debug Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill debug-arbiterforge
This Skill investigates unknown defects, anomalies, and unexpected behavior when the cause is not yet understood. It helps teams avoid guesswork by forcing evidence-backed diagnosis before any fix is attempted.
Use the debug skill to investigate the reported failure, collect a minimal repro, and route the outcome to the correct follow-up action.
High-intent search queries and answers about installing and using this skill.
Find the root cause of an intermittent anomaly by capturing symptoms and forming competing hypotheses, including environmental explanations, before narrowing down the cause. Evidence is gathered from logs, traces, and configuration in a read-only way to prevent guesswork.
The best way to debug intermittent anomalies is to apply a disciplined root-cause workflow that requires multiple distinct hypotheses and cited evidence from logs or traces. This evidence-gated process ensures you understand the failure before acting.
Structure a debugging investigation by first capturing the symptom and reproduction steps, then forming multiple hypotheses. Gather cited evidence from read-only logs, commits, and configuration to decide whether to route the outcome to fix, adr, or no-action close.
Yes, you can use logs and traces to diagnose unexpected behavior without applying a fix. The investigation process requires read-only analysis of logs, traces, commits, and configuration to gather evidence and decide the correct downstream routing action.
You should close a debugging session with no-action instead of routing to a fix when the evidence-gated analysis of logs, traces, and configuration proves the reported defect or unexpected behavior does not require a code change or architecture review.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
tonombDiagnose software bugs through a six-phase feedback-loop methodology.
ascerra-fullsend-rehearsalCreate and manage Architecture Decision Records for software architecture.
a29paulMonitor production deployments for console errors, performance regressions, and visual anomalies.
