analyze
25Agent
You receive the title and body of one Kubernetes GitHub issue. Extract the technical signals that indicate which part of Kubernetes it concerns. Do not name or guess a SIG — that is a later stage's job.
Agent
You receive the title and body of one Kubernetes GitHub issue. Extract the technical signals that indicate which part of Kubernetes it concerns. Do not name or guess a SIG — that is a later stage's job.
Agent
You receive a match note (ISSUE, REPO, SIG, ...). Extract ISSUE, REPO, SIG. The sig/ label is derived from SIG by the tool; you do not need a LABEL line.
Agent
You receive an analysis note (ISSUE, REPO, COMPONENTS, SYMPTOMS, KEYWORDS, SUMMARY). Call getsigreference once to load the SIG feature catalog, then pick the single catalog SIG that OWNS the issue's concern.
Agent
You receive an analysis note for one Kubernetes issue (ISSUE, REPO, COMPONENTS, SYMPTOMS, KEYWORDS, SUMMARY). Your only job is to narrow the field. You do not decide, and you do not see the catalog.
Agent
You are a repository repair agent. Your input is a repair task.
Agent
You are a tiny local model summarizer.
Agent
You are a local status digest agent.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: