Enforce a root-cause investigation workflow with structured evidence and stage gates.
npx skills add https://github.com/KaimingWan/oh-my-kiro --skill omk-debugging
Please help me install this Agent Skill. Skill: omk-debugging Source: https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-debugging Command: npx skills add https://github.com/KaimingWan/oh-my-kiro --skill omk-debugging
Systematic debugging framework that enforces a disciplined, evidence-based approach to diagnose and fix bugs, reducing time to root cause.
Start a debugging session by creating an investigation document and following the four phases to trace root causes.
High-intent search queries and answers about installing and using this skill.
Systematic debugging enforces a root-cause investigation workflow by requiring diagnostic evidence collection through get_diagnostics and symbol searches before patching. It progresses through defined phases: Root Cause, Pattern Analysis, Hypothesis Testing, and Implementation.
The best way to debug unexpected test failures is using a structured investigation template to capture findings. This workflow requires tracing data flow with goto_definition and search_symbols to build an L0-L2 evidence system before making code changes.
An evidence-based debugging workflow handles pattern analysis by gating investigation phases, ensuring you trace data flow and collect diagnostics before forming hypotheses. It uses a rigorous decision log to map symptoms to root causes systematically.
Yes, you can use this debugging framework for any non-trivial debugging scenario, including crashes and unexpected behavior, across codebases and environments. It applies safety rails requiring diagnostic evidence collection before progressing to implementation.
You should avoid a systematic debugging workflow for trivial fixes where the root cause is immediately obvious. It is designed for non-trivial scenarios requiring structured evidence collection, pattern analysis, and phase-driven validation before patching.
kenlckBuild a persistent graph of TypeScript/JavaScript files, symbols, and edges.
JamieMasonReproduces and debugs issues in the Swagger codebase using AI-powered analysis and automated correction suggestions.
fratilanicoTrace bugs to root causes through call chains and data flow.
YangYuS8Identify and isolate root causes of bugs before proposing fixes.
