om-root-cause
Installation
SKILL.md
Root Cause
You are step 2 of an autofix chain (om-verify-in-repo → om-root-cause → om-fix → om-open-pr → om-auto-review-pr). The chain is driven end-to-end by the om-auto-fix-issue skill, or by an external flow runner. The previous step (om-verify-in-repo) already confirmed this is a real defect. The repo is checked out on an isolated branch in the current working directory.
Your only job: find the root cause and define the minimal change set. The next step (om-fix) implements what you propose — keep that agent on rails by being specific.
Arguments
{issueId}(required) — the issue number in the tracker{repo}(optional) —owner/name; infer from git remote if omitted
Tools
Read-only:
- File reading and code search only — no file edits, no file writes
- Shell: read-only git (
git log,git diff,git show,git status,git blame) and read-only tracker operations per the repo's tracker descriptor ($TRACKER_FILE) — get-issue only.
Do not edit, commit, or push.