From x-bug-triage-plugin
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.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin x-bug-triage-pluginThis skill is limited to using the following tools:
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.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
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.
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.
config/routing.json (precedence modifiers, staleness threshold)mcp__triage__lookup_* tool callsFor each cluster, check if a routing_override exists from a prior run:
For each cluster without an override, query sources strictly in order:
| Level | Source | Tool | Base Confidence |
|---|---|---|---|
| 1 | Service owner | mcp__triage__lookup_service_owner | 1.0 |
| 2 | Oncall | mcp__triage__lookup_oncall | 0.9 |
| 3 | CODEOWNERS | mcp__triage__parse_codeowners | 0.8 |
| 4 | Recent assignees (30d) | mcp__triage__lookup_recent_assignees | 0.6 |
| 5 | Recent committers (14d) | mcp__triage__lookup_recent_committers | 0.5 |
| 6 | Fallback mapping | Config lookup | 0.3 |
Stop at the first level that returns a valid team or assignee.
Multiply each result's confidence by the precedence modifier from routing_config.
Flag any routing signal older than the staleness threshold (default 30 days):
Using lib.buildRoutingRecommendation():
cluster_routing rows with ranked candidates (team/assignee, source level, confidence, staleness flag)top_recommendation field set on each cluster (or null with uncertainty=true if no signals)Triggered automatically by the owner-router agent after clusters are produced. Typical run output for a 12-cluster batch: "12 clusters routed — 1 via override, 4 via service-owner, 3 via oncall, 2 via CODEOWNERS, 2 via recent committers, 0 via fallback (1 stale signal flagged)".
Load routing precedence rules:
!cat skills/x-bug-triage/references/routing-rules.md
Load escalation trigger definitions:
!cat skills/x-bug-triage/references/escalation-rules.md