Identify failure root causes from logs and runtime evidence.
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-debug-shimamatz
Please help me install this Agent Skill. Skill: kiro-debug Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-debug Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-debug-shimamatz
This skill helps engineers investigate implementation failures by focusing on root causes rather than patching symptoms, enabling structured, evidence-based remediation.
Provide the exact failure symptom, runtime context, and failing commands to begin root-cause analysis.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a software failure, gather exact failure symptoms, runtime context, and logs to classify the fault and validate hypotheses before proposing a minimal, verifiable remediation plan.
The best way to debug a repeatedly failing task is using structured, evidence-driven investigation to isolate the exact root cause from local runtime inspection and design a concrete remediation plan with guardrails.
To reproduce and classify a fault, assess local runtime evidence, logs, and current changes against the exact failure symptom and environment to determine the root cause across common scenarios.
Your software incident keeps recurring because symptom patches do not address the root cause; evidence-driven remediation validates hypotheses using runtime inspection to design a minimal, verifiable fix.
To start troubleshooting a blocking implementation failure, you need to provide the exact failure symptom, runtime context, and failing commands to begin evidence-based root-cause analysis.
Yes, you can get a remediation plan with verification steps and guardrails by identifying the exact failure symptom to determine the root cause and providing a concrete, minimal fix plan for safe task progression.
derHakenTrace data flow and apply a four-phase process to fix root causes.
HahyeonJeonGuide executors through study, plan, execute, verify, and final reporting stages.
huyhung9630Generate hypotheses and gather evidence to trace software issues to their root cause.
LuizfbmInvestigate software defects by mandating root cause analysis before implementing fixes.
