Identify and remediate software errors using a structured debugging workflow with verified tool outputs.
npx skills add https://github.com/duggal1/Sapphire-cli --skill debug-duggal1
Please help me install this Agent Skill. Skill: debug Source: https://github.com/duggal1/Sapphire-cli/tree/main/internal/skills/bundled/debug Command: npx skills add https://github.com/duggal1/Sapphire-cli --skill debug-duggal1
This skill provides a disciplined, tool-backed approach to identifying, isolating, and remediating software errors by requiring traceable evidence from executed steps and results.
Begin a guided debugging session by outlining the failure boundary and requesting a verified plan with step-by-step tool outputs.
High-intent search queries and answers about installing and using this skill.
To debug software errors with verifiable evidence, apply a structured workflow that reproduces failure boundaries, collects terminal and codebase outputs, and validates fixes using auditable traces. This enforces a full tool-chain mandate for root-cause isolation.
Troubleshooting a flaky deployment requires running the full tool-chain—web search, codebase reading, terminal execution, and file inspection—to verify the root cause. You confirm a reproducible fix by validating the remediation with collected logs.
Isolating failure boundaries during incident response involves executing terminal commands and reading the codebase to trace errors. You reproduce the issue, collect tool outputs, and validate the fix with auditable evidence.
Yes, you can use terminal execution and file inspection to verify a software fix. The debugging workflow mandates tool execution to drive evidence-based conclusions, ensuring fixes are validated with auditable outputs.
Structured troubleshooting works across codebases and runtime environments by reproducing issues and collecting tool outputs. It enforces a full tool-chain mandate, including web fetch and codebase reading, to surface root causes.
Debugging without a full tool-chain mandate limits your ability to isolate failure boundaries and validate fixes with auditable traces. It skips necessary evidence collection from web searches, terminal execution, and file inspection.
mgkyawzayyaDiagnose container agent issues by inspecting logs, mounts, and environment variables.
cslsoftwaresCoordinate production-incident response with severity classification and post-mortem documentation.
CygnusfearControl Chrome DevTools Protocol to automate browser interactions and capture console, network, and screenshots.
tonone-aiDiagnose production incidents by analyzing logs, metrics, and traces to identify root cause.
