Agent skill · operations · jeremylongshore
owner-routing
Internal process for the owner-router agent. Defines the step-by-step procedure for determining likely bug owners using strict 6-level routing precedence with staleness detection. Not user-invocable — loaded by the owner-router agent through its skills frontmatter.
Why this skill is useful
Adds a detailed internal routing procedure for bug ownership that the AI wouldn't generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Owner Routing Process Step-by-step procedure for determining the most likely owner/team for each bug cluster using strict 6-level precedence with staleness detection and override memory. Overview Loaded by the owner-router agent inside the x-bug-triage plugin. Walks each open bug cluster through a deterministic six-level routing precedence (service-owner → oncall → CODEOWNERS → recent assignees → recent committers → fallback mapping), applies confidence modifiers, detects stale signals, and produces a ranked routing recommendation. Honors prior routing overrides recorded in cluster memory before consulting any signal source. Prerequisites Cluster table populated upstream by the bug-clustering stage Routing config available at config/routing.json (precedence modifiers, staleness threshold) Triage MCP server reachable for mcptriagelookup tool calls Repos in the cluster's productsurface have a configured surface→repo mapping Instructions Step 1: Check Overrides First For each cluster, check if a routingoverride exists from a prior run: If found: use the override (confidence 1.0, source "routingoverride"), skip precedence lookup Log the override application to audit Step 2: Query Sources in Precedence Order For each cluster without an override, query sources strictly in order: Level Source Tool Base Confidence ------- -------- ------ ---------------- 1 Service owner mcptriagelookupserviceowner 1.0 2 Oncall mcptriagelookuponcall 0.9 3 CODEOWNERS mcptriageparsecodeowners 0.8 4 Recent assignees (30d) mcptriagelookuprecentassignees 0.6 5 Recent committers (14d) mcptriagelookuprecentcommitters 0.5 6 Fallback mapping Config lookup 0.3 Stop at the first level that returns a valid team or assignee. Step 3: Apply Confidence Modifiers Multiply each result's confidence by the precedence modifier from routingconfig. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/owner-routing