skills.rest
triage-software
triage-softwareOFFICIAL
Explore all skills by this author →
GitHub

ot-root-cause

Diagnose tracker-reported bugs and define the minimal code change set.

Updated Sep 10, 2026
Search Tags:#git#root cause analysis#code search#github issues#bug diagnosis#regression test#autofix pipeline
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-root-cause-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-root-cause
Source: https://github.com/triage-software/skills/tree/main/skills/ot-root-cause
Command: npx skills add https://github.com/triage-software/skills --skill ot-root-cause-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigating a bug report from scratch burns time and context: an agent must re-read the issue, hunt through the codebase, and guess at the fix scope. This Skill performs read-only root-cause analysis on a confirmed tracker issue and hands the next agent a precise, implementation-ready brief. ## Core Features & Use Cases - Root-Cause Tracing: Pulls the issue from the tracker, reads just enough project context, and traces the failing code path down to file and line evidence. - Minimal Change Definition: Identifies the smallest module or function that owns the bug, lists exact files to change, and proposes a regression test — no scope creep or drive-by refactors. - Structured Handoff Report: Outputs a fixed-format plain-text brief (Summary, Root cause, Files to change, Approach, Risks) that the downstream ot-fix skill consumes verbatim, with a LOW_CONFIDENCE token when the cause is inferred. - Use Case: In an automated issue-to-PR pipeline, after a defect is verified in the repo, run this Skill to produce the diagnosis brief so the fix agent can implement directly without re-exploring the codebase. ## Quick Start Run the ot-root-cause skill on issue 142 to analyze the bug and produce a minimal-change brief for the fix step.

Frequently Asked Questions about ot-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 GitHub issue?▼

Run this Skill with the issue number; it fetches the issue via the tracker get-issue operation, traces the failing code path with read-only git and code search, and reports the root cause with file:line evidence plus the minimal files to change.

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

The report contains five fixed fields: Summary, Root cause with file:line evidence, Files to change including a regression test, a 1-3 sentence Approach, and Risks. The downstream ot-fix skill reads this brief verbatim, so field names are preserved exactly.

Can this Skill modify code or tracker state during analysis?▼

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 labels and claims.

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

The Skill ends its report with the LOW_CONFIDENCE token and a best-guess analysis. The autofix chain continues, but the flag signals that a human reviewer should check the resulting fix more carefully.

Does root-cause analysis require repository configuration first?▼

Yes. The Skill loads .ai/agentic.config.json and the tracker descriptor during preflight; if they are missing, it runs the ot-setup-agent-pipeline skill first. The repo must already be checked out on an isolated branch by the chain driver.

Related Skills

Explore More Software Engineering Skills→
go-musicfoxgo-musicfox
2.6k

om-verify-in-repo

Triage tracker issues read-only to decide whether an autofix chain should proceed.

Official
Advanced
Femad-6Femad-6

code-review

Review code changes and diffs with severity-ranked findings and minimal fix suggestions.

Community
Intermediate
CityBear3CityBear3

commit

Generates Git commit messages by analyzing staged/unstaged diffs and recent history.

Community
Intermediate
big4council-progbig4council-prog

node-inspect-debugger

Control Node.js breakpoints and inspect runtime state via the inspector protocol.

Community
Advanced