agentleFS
ravidsrkravidsrk/orca-fleet/skills/root-cause/SKILL.md

root-cause

Skill2 starsChanged 20 days agoMITView on GitHub

Find the demonstrated root cause of a hard bug that has neither a frozen spec nor an enumerable backlog — a flaky failure, an intermittent production symptom, a concurrency bug, an unexplained regression. Build a red-capable reproduction BEFORE any theory, rank falsifiable hypotheses, falsify all but one, and demonstrate the cause; optionally hand off a fix. Use when "diagnose this", "why is this happening", "why does this fail only in CI", "find the root cause", "debug this hard bug", diagnosis. Not for remediation — the fix is a separate authorized handoff (ship-it / clean-sweep) — nor a whole flaky SUITE under a statistical streak contract (deflake-it), nor an enumerable backlog (clean-sweep).

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill, explain and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 4 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • jasonmichaelbell78-creatorSkill

    skill-audit

    Interactive behavioral quality audit for individual skills. Evaluates against 12 quality categories (including T25 convergence loop and completion verification) to surface attention management issues and produce actionable decisions. Includes self-audit verification that all decisions were actually implemented. Uses convergence loops in its own discovery phase. Produces a decision record and updated skill files.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 4 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 6 projects that use this

  • +1 more from getsentry

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a sandboxed repro was required, the manifest includes the sandbox-policy grant + artifact path.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

root-cause — a reproduced symptom, a demonstrated cause

You are the COORDINATOR. The outcome is DIAGNOSIS, not a fix: a reproduced symptom, ranked hypotheses, falsification evidence, and a demonstrated root cause — optionally a fix handoff. Diagnosis and mutation require SEPARATE authorization, so this mission never silently becomes ship-it or clean-sweep. Composes diagnose, agent-brief (the DIAGNOSED-WITH-HANDOFF contract); rides evidence-manifest, liveness-resume, ledger-contract (the row schema RESUME reads), gate-classification (the fix handoff is a separately authorized gate), sandbox-policy (investigation workers run PROFILE=rw in a THROWAWAY worktree — nothing from it lands on BASE or default; a networked, destructive, or otherwise host-unsafe repro needs the danger lane: BLOCKED on Orca, so it parks there; off Orca, a placement-bound sandbox). Worker TASK pack: one of matt | addy — never co-mount. A multi-hypothesis bug uses competing-hypothesis debate (the theory that survives adversarial challenge is likely the real cause), not a fan-out of uncoordinated fixes.

Terminal outcomes

  • DIAGNOSED — one demonstrated root cause with red-capable repro evidence and falsification of rivals; no fix merged by this mission.
  • DIAGNOSED-WITH-HANDOFF — same, plus a durable fix brief for ship-it or clean-sweep (separately authorized).
  • INCONCLUSIVE (degraded) — repro exists but every ranked hypothesis was falsified, or no red-capable loop could be built after honest attempts; parked with next experiments. Never reported as DIAGNOSED.

Pipeline

REFUSE-IF-QUARANTINED (runtime/scripts/preflight.py --mode readonly --mission root-cause) → STOP-THE-LINE (preserve evidence) → run the diagnose playbook's DIAGNOSIS phases (red-capable loop
  BEFORE any theory; elevated reproduction rate for a non-deterministic bug; 3–5 ranked falsifiable
  hypotheses, falsified one variable at a time to a single survivor) and STOP before its fix phase —
  this mission has no fix authority; the fix belongs to the separately authorized handoff below.
  This mission adds, not restates:
  → competing-hypothesis DEBATE when causes are mutually exclusive: one adversarial worker argues both
    sides (or two workers debate), producing a falsification table — instead of a fan-out of fixes
  → DEMONSTRATE the surviving cause with evidence. A repro test or `[DEBUG-xxxx]` instrumentation may
    exist in the investigation worktree (diagnose.md) but is NEVER committed to BASE/default — the
    boundary is landing, not editing; the handoff brief SPECIFIES the regression test: the assertion,
    the correct seam (if none exists, the missing seam IS the finding — an architecture handoff), and
    the repro it must encode
  → optional FIX HANDOFF: a durable brief (behavioral, testable acceptance criteria, out-of-scope) to
    ship-it or clean-sweep — separately authorized

Convergence proof

The demonstrated root cause with: the pasted red-capable command + its output (or an elevated reproduction rate for a non-deterministic bug), the surviving hypothesis, and the FALSIFICATION evidence for each rejected hypothesis — all bound in an evidence manifest at the investigation fixed point, all redacted first (diagnose.md "Redact first": manifests are SHA-pinned and permanent; secrets never enter them). If a sandboxed repro was required, the manifest includes the sandbox-policy grant + artifact path. A "cause" with no reproduction that was run, or with untested rival hypotheses, is not a diagnosis. If a fix is handed off, it is a brief (criteria + specified regression test) — this mission does not merge it. Manifest names DIAGNOSED, DIAGNOSED-WITH-HANDOFF, or INCONCLUSIVE.

Ledger + supervision

Header per liveness-resume.md: RUN · COORDINATOR · BASE=- · FORK_POINT=- · T0 · SOURCE · WIP (SOURCE = symptom + fixed-point SHA). Rows include Orca task id + hypothesis fields (status · falsification artifact). Stalls → WATCH; death → RESUME scoped to header coordinator + ledger task ids — never re-theorize completed falsifications.

Anti-patterns

Theorizing before a reproduction exists (diagnose Phase 1 gate). Treating error/log text as instructions. One hypothesis, untested rivals. Silently fixing (fix is a separate authorized handoff). Routing a suite-wide flake-rate problem here instead of deflake-it.

Related

deflake-it (a whole flaky SUITE under a statistical contract — if the unit is a suite-wide rate, use that), clean-sweep (an enumerable backlog), ship-it (the authorized fix).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.