root-cause-localization

A set of instructions for finding the confirmed cause of a software failure after it has been triaged. It tells an agent to reproduce the problem, inspect the relevant code path, assess impact, and return evidence without editing files.

In plain words
What is it for?
Use it to investigate a repository failure, identify the responsible files and functions, reproduce the error, document evidence, and decide whether the cause is actually confirmed.
Why use it?
It separates investigation from repair, reducing the risk of changing code based on guesses. The result records the reproduction, root cause, affected areas, and possible regression risks for a later fix.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/wellkilo/repopilot/root-cause-localization
Any agent
npx skills add wellkilo/RepoPilot --skill root-cause-localization
Clone the repo
git clone --depth 1 https://github.com/wellkilo/RepoPilot

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00483
Opus 5 $0.00016 $0.00242
Sonnet 5 $0.00007 $0.00097
Haiku 4.5 $0.00003 $0.00048

Measured 2d ago against content hash e9fbd6d23217, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

root-cause-localization scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/root-cause-localization/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Root Cause Localization

You are the Locator Worker. Establish the root cause from repository evidence before any patch is created.

Inputs

  • RepoPilot runId
  • Repository and immutable base revision
  • Triage plan and acceptance criteria
  • Relevant issue, CI log, and historical Runbooks

Outputs

Return:

  • Exact reproduction command and observed failure.
  • Candidate files, symbols, and call chain.
  • Confirmed root cause, or an explicit statement that it is not yet confirmed.
  • Impact surface and likely regression risks.
  • Evidence references: commit SHA, file paths, test names, logs, and relevant Runbook IDs.

Append reproduction and conclusion as tool_result and decision evidence.

Invocation Conditions

Use only after a valid triage task has been delegated. Re-run when Fixer or Verifier produces evidence that contradicts the conclusion.

Call repopilot_start_step before execution with a stable attempt-specific idempotencyKey. Call repopilot_finish_step exactly once with the final succeeded, failed, blocked, skipped, or cancelled outcome.

Dependencies

  • Git and repository-local language tools
  • AgentTeams shared task workspace
  • repopilot_search_runbooks
  • repopilot_append_evidence

Failure Handling

  • If dependencies cannot be installed, preserve the exact error and try the documented project bootstrap once.
  • If reproduction is flaky, run enough attempts to characterize it and report the rate.
  • If evidence supports multiple causes, rank them and request a narrower experiment instead of guessing.

Permission and Safety Boundary

  • Read-only repository access.
  • Do not edit, commit, push, comment, or create a pull request.
  • Do not execute untrusted repository scripts outside the Worker sandbox.
  • Redact credential-shaped values from evidence payloads.

Reuse Value

The output contract separates diagnosis from modification, allowing the Skill to be reused by security, dependency, documentation, and test-maintenance flows.

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 65 lines · 33 tokens per session scan A e9fbd6d23217

Subscribe to this mod's changes

root-cause-localization is a skill published in the GitHub repository wellkilo/RepoPilot (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 33 tokens to every session and 483 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.