What problem does it solve? When an issue is confirmed as a real defect, someone still has to dig through the repository to find where the bug lives and what should change. This Skill performs that read-only root-cause analysis so the next agent in an automated fix chain can implement the fix without re-exploring the codebase. ## Core Features & Use Cases - Read-only investigation: Pulls the issue via the tracker get-issue operation, reads project docs, and traces the code path using only file reads and read-only git commands. - Minimal change definition: Identifies the smallest module or function that owns the bug and lists exact files to change, including regression tests. - Structured handoff report: Produces a plain-text report with summary, root cause, files to change, approach, and risks that the om-fix step consumes verbatim. - Use Case: In an autofix chain (om-verify-in-repo → om-root-cause → om-fix → om-open-pr), after an issue is verified as a real bug, this Skill locates the faulty function and hands a precise fix plan to the implementation agent. ## Quick Start Run the om-root-cause skill with the issue number to analyze the confirmed bug and produce a root-cause report for the fix agent.
