Triage Prs
Productivitytriage-prsTriage Prs is an Agent Skill for productivity published in the docker/docker-agent repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Triage open pull requests on docker/docker-agent — apply area/* and kind/* labels, flag merge conflicts (draft + status/needs-rebase + author comment), and clear the needs-rebase label once conflicts are resolved. Idempotent and API-frugal; designed to run on a recurring schedule.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/docker/docker-agent/blob/HEAD/.agents/skills/triage-prs/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/triage-prs, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Triage Pull Requests
Triage open pull requests on the docker/docker-agent repository: classify them
with area/* and kind/* labels, flag those with merge conflicts, and clear the
conflict flag once it is resolved.
This skill is designed to run unattended on a recurring schedule (every ~30 minutes). It is written to be agent-agnostic — use whatever GitHub access you have (CLI, REST, GraphQL, an MCP server). Two properties matter more than the mechanism and must hold no matter how you talk to GitHub:
- Idempotency is critical. The skill runs repeatedly. A given PR must never be re-drafted, re-labeled, or re-commented if it is already in the desired state. Re-running over the same PRs must produce zero changes and, ideally, zero write calls.
- Minimize GitHub API calls. Read once, decide everything in memory, then make the smallest possible number of writes — see API budget.
Scope
Process open pull requests (including author-created drafts) whose last update was within the past 60 minutes.
Out of scope — skip entirely:
- Closed and merged PRs.
- PRs untouched in the last 60 minutes.
The 60-minute window against the ~30-minute cadence intentionally gives every PR two chances to be processed, so a single missed or failed run is harmless.
⚠️ Never trust GitHub's search index for decisions.
is:pr label:…search filters (and thegh --label/search/issuesAPIs that back them) are stale: they return PRs that no longer carry a label and miss PRs that do. Before acting on any PR, read that PR's live, per-item fields (labels, draft state, mergeable state). Use search only as a coarse pre-filter, never as the source of truth for a mutation.
API budget
- One read pass. Fetch the in-scope candidate set in a single batched query
(GraphQL is ideal). For each PR retrieve everything all three rules need at once:
updatedAt,isDraft, andmergeablestate (MERGEABLE/CONFLICTING/UNKNOWN)- the current set of labels (live)
title,body, and linked issues viaclosingIssuesReferences, including each linked issue's labels and native issue type- the changed files / paths (to infer
area/*) - whether a previous run already posted the conflict comment (to gate re-commenting) — e.g. detect an existing bot comment
- Decide fully in memory. For each PR, compute the complete set of mutations for all three rules before issuing any write.
- One grouped label mutation per PR. Fold every label change for a PR — adding
area/*, addingkind/*, and adding or removingstatus/needs-rebase— into a single label update call. Never issue one call per label. - No-op means no call. If a PR needs no change, make zero write calls for it.
UNKNOWNmergeable → do nothing this run. GitHub computes mergeability asynchronously. If the state isUNKNOWN, skip the conflict rules for that PR; it will be re-evaluated next run once GitHub finishes. (You may still apply Rule 1 labels, which do not depend on mergeability.)
Label taxonomy
Use only labels that already exist in the repository. Never invent a label. If
the appropriate label does not exist or the correct value is genuinely ambiguous,
leave that dimension alone (optionally apply status/needs-triage) rather than
guessing.
kind/* — the change type (exactly one on a PR)
kind/feat— adds a new feature (Conventional-Commitfeat:).kind/fix— fixes a bug (Conventional-Commitfix:).kind/docs— documentation-only change.kind/chore— maintenance, deps, CI, tooling (chore:).kind/refactor— refactor with no behavior change (refactor:).kind/test— test-only change (test:).kind/security— security fix or hardening.
kind/featandkind/fixare the canonical labels — they map to the repo'sfeat:/fix:commit convention. The olderkind/featureandkind/buglabels have been deleted; never apply them.
kind/*is for pull requests only. Issues use GitHub's native issue type field (Task,Bug,Enhancement,Epic,Initiative) and must never carry akind/*label. When a linked issue informs a PR's kind (see Rule 1), read its native issue type, not akind/*label.
area/* — the part of the codebase touched (one or more on a PR)
Infer from the changed paths. Valid values (do not invent others):
area/a2a, area/agent, area/api, area/ci, area/cli, area/config,
area/core, area/deps, area/distribution, area/docs, area/gateway,
area/mcp, area/models, area/providers, area/providers/anthropic,
area/providers/bedrock, area/providers/docker-model-runner,
area/providers/gemini, area/providers/openai, area/rag, area/registry,
area/runtime, area/security, area/sessions, area/skills, area/telemetry,
area/testing, area/tools, area/tui.
For Docker Model Runner work, use
area/providers/docker-model-runner. The legacy top-levelarea/docker-model-runnerhas been deleted; never apply it.
Path-hint examples: pkg/config/** → area/config; TUI code → area/tui;
.github/workflows/** → area/ci; MCP server/tooling → area/mcp or area/tools;
provider integrations → the matching area/providers/*; docs/markdown → area/docs.
status/*
status/needs-rebase— the PR has merge conflicts / is out of date with the base branch. Applied and removed by this skill (Rules 2 and 3).status/needs-triage— optional fallback when a PR'skind/*orarea/*cannot be determined with confidence.
Rule 1 — Apply area/* and kind/*
Trigger: an in-scope PR missing an area/* label and/or a kind/* label.
Skip if: the PR already has at least one area/* and one kind/* label
(consider it triaged for those dimensions).
Action — add only the missing dimension:
kind/*(a PR should have exactly one), inferred in this priority order:- If the PR closes/links an issue, use that issue's native issue type to guide
the kind:
Bug→kind/fix;Enhancement→kind/feat. (Use the PR's own signals below to refine, e.g. a docs-only PR closing an Enhancement is stillkind/docs.) - Otherwise infer from the Conventional-Commit prefix in the PR title
(
feat:→kind/feat,fix:→kind/fix,docs:→kind/docs,chore:→kind/chore,refactor:→kind/refactor,test:→kind/test), and from the PR title/body intent.
- If the PR closes/links an issue, use that issue's native issue type to guide
the kind:
area/*— infer one or more from the files/paths the PR changes.
Guard rails:
- Add only the missing dimension. Never remove or overwrite an
area/*orkind/*label that a human already set. - Use only existing repository labels (see taxonomy); never invent one.
- If
kind/*orarea/*is genuinely ambiguous, leave that dimension unset (optionally addstatus/needs-triage) rather than guessing. - Fold these label additions into the PR's single grouped label mutation, together
with any
status/needs-rebasechange from Rules 2/3.
Rule 2 — Flag merge conflicts
Trigger: an in-scope PR whose live mergeable state is CONFLICTING.
Idempotency gate (critical): if the PR already has status/needs-rebase, do
nothing for this rule — do not re-draft, do not post another comment.
Action (first time only):
-
Convert the PR to draft — skip this step if the PR is already a draft (the
isDraftfield from the read pass tells you; converting an already-draft PR is a no-op write and violates the "no-op means no call" budget rule). -
Add
status/needs-rebase(in the same grouped label mutation as any Rule 1 labels). -
Post one comment addressed to the author, for example:
👋 This PR has merge conflicts with the base branch. Please rebase or merge the latest base branch and resolve them. I've moved it to draft and added
status/needs-rebase; it'll be picked back up automatically once the conflicts are cleared.
Because the label, the draft conversion, and the comment are always applied together,
the presence of status/needs-rebase is a reliable signal that the comment was
already posted — use it as the gate to avoid duplicate comments.
Rule 3 — Clear resolved conflicts
Trigger: a PR that currently has status/needs-rebase whose live mergeable state
is now MERGEABLE.
Action: remove status/needs-rebase (fold into the PR's single grouped label
mutation).
Do not:
- trigger on
UNKNOWNmergeable state — onlyMERGEABLEclears the label. If the state isUNKNOWN, leavestatus/needs-rebasein place and re-evaluate next run (see the API budgetUNKNOWNrule); never treatUNKNOWNas resolved, - mark the PR ready for review (leave the draft/ready state to the author), and
- post any comment.
Execution summary
For each in-scope PR, in one read-then-write cycle:
- Read its live fields (labels,
isDraft,mergeable, linked-issue types, changed paths, prior bot comment). - Compute the combined set of changes from Rules 1–3 in memory:
- missing
kind/*/area/*to add (Rule 1), status/needs-rebaseto add + draft + comment if newlyCONFLICTINGand not already flagged (Rule 2),status/needs-rebaseto remove if flagged and nowMERGEABLE(Rule 3).
- missing
- Apply one grouped label mutation for all label changes, plus at most one draft conversion (only if newly drafting a not-already-draft PR) and at most one comment. Skip every PR that needs nothing.
Report
After the run, output a concise summary of what changed:
- PRs newly labeled, with the
area/*/kind/*added per PR. - PRs newly flagged
status/needs-rebase(drafted + commented). - PRs cleared of
status/needs-rebase. - PRs skipped because mergeable state was
UNKNOWN(to be retried next run). - Any PR left for human triage (ambiguous
kind/*/area/*).
If nothing changed, say so explicitly — for an idempotent run over already-triaged PRs, "no changes" is the expected and correct outcome.