What problem does it solve? When an automated bug-fix pipeline picks up a confirmed defect, the fixing agent often wastes its budget re-exploring the repository. This Skill performs read-only root-cause analysis on a tracker issue, pinpointing the exact files and minimal change surface so the next agent can implement the fix directly. ## Core Features & Use Cases - Read-only investigation: Uses only file reading, code search, read-only git commands (log, diff, blame), and the tracker get-issue operation — never edits, commits, or pushes. - Structured handoff report: Produces a fixed-format brief (Summary, Root cause, Files to change, Approach, Risks) that the downstream om-fix step consumes verbatim. - Minimal-change discipline: Identifies the smallest module or function owning the bug, avoids refactors, and flags low-confidence analyses with a LOW_CONFIDENCE marker. - Use Case: As step 2 of an autofix chain (om-verify-in-repo → om-root-cause → om-fix → om-open-pr), it takes issue #142, traces the failing code path, and hands om-fix a precise plan naming the two source files and one regression test to change. ## Quick Start Run the om-root-cause skill with the issue number, for example: analyze issue 142 and produce a root-cause report for the fix agent.