owner-routing

Determine bug cluster owners using six-level routing precedence with staleness detection.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill owner-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owner-routing
Source: https://github.com/jeremylongshore/x-bug-triage-plugin/tree/main/skills/owner-routing
Command: npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill owner-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates owner attribution for bug clusters by applying a strict 6-level routing precedence with staleness checks, reducing manual triage effort.

Core Features & Use Cases

  • 6-level routing precedence with override memory to determine the most likely owner.
  • Staleness detection and confidence modulation to keep ownership mappings fresh.
  • Non-user-invocable integration loaded by the agent, with auditability and deterministic outputs.

Quick Start

Run the owner-routing process on a bug cluster to assign the most likely owner using six routing levels.

Frequently Asked Questions about owner-routing

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

FAQPage Schema
How do I automate bug triage and assign owners for clusters across a codebase?

Automate bug triage by applying a deterministic six-level routing precedence to clusters, checking service owner, oncall, CODEOWNERS, recent assignees, recent committers, and fallback mapping. This identifies the most probable owner and reduces manual effort.

What is the best way to determine bug ownership using recent committers and CODEOWNERS?

Determine bug ownership using a six-level routing precedence that evaluates CODEOWNERS and recent committers alongside oncall and service owner data. A staleness threshold, defaulting to 30 days, modulates confidence to keep mappings fresh.

How does staleness detection work when routing bug assignments to oncall or service owners?

Staleness detection applies a 30-day default threshold to ownership mappings, modulating confidence if assignments are outdated. It evaluates six routing levels including service owner and oncall, automatically overriding stale assignments with auditability.

Can I override the default routing precedence for a specific bug cluster assignment?

Override the default routing precedence using the built-in override memory, which allows manual adjustments to the six-level routing chain. The buildRoutingRecommendation helper then produces a top recommendation incorporating your overrides.

Does owner-routing integrate as a non-user-invocable process loaded by an agent at runtime?

Owner-routing integrates as a non-user-invocable process loaded by the agent at runtime, applying its six-level routing precedence to bug clusters. It provides deterministic outputs with full auditability for engineering triage workflows.

What are the limitations of relying on fallback mappings for bug owner triage?

Fallback mappings represent the sixth and lowest priority level in the routing precedence chain, used only when service owner, oncall, CODEOWNERS, recent assignees, and recent committers fail. Relying on them indicates all higher-confidence ownership data is missing or stale.