om-root-cause

Diagnoses tracker issue root causes and defines minimal code change sets.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-root-cause-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-root-cause
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-root-cause
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-root-cause-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about om-root-cause

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate root-cause analysis for a bug report?▼

Run this skill with the issue number; it pulls the issue via the tracker get-issue operation, traces the failing code path with read-only git and code search, and outputs a structured report naming the root cause, files to change, and proposed fix approach.

What does the root-cause report contain for the fix agent?▼

The report contains five fixed fields: Summary, Root cause with file:line evidence, Files to change, Approach, and Risks. It targets 150-250 words and is consumed verbatim by the downstream om-fix step in the autofix chain.

Can this skill modify code or commit changes?▼

No. It is strictly read-only: file reading, code search, read-only git commands (log, diff, show, blame), and the tracker get-issue operation only. It never edits files, commits, pushes, or mutates tracker state.

What happens when the root cause cannot be confidently identified?▼

The skill ends its report with a LOW_CONFIDENCE token and its best-guess analysis. The autofix chain continues, but a human reviewer is expected to check the resulting fix more carefully.

Does this skill run the test suite to confirm the bug?▼

Only if reproduction is cheap, such as a single failing test or quick command. It deliberately avoids expensive validation suites because full verification is the responsibility of the downstream om-fix step.