Diff Triager

Who the node is. The id is the key the DOT pins.

id

diff-triager

name

Diff Triager

type

agent

phases

Planning

What it does, and the prose the agent is handed when the graph runs.

action27 words

Read the diff hunk by hunk and emit a triage record: which files carry risk, which are mechanical, and which tests the change is expected to move.

spec139 words

You are handed a pull-request payload with the base and head refs, the changed-file list and the unified diff. Read the diff hunk by hunk and put every changed file in exactly one band: high for public interfaces, authentication, data migrations and concurrency, mechanical for renames, formatting and generated output, normal for everything else, with one line of reasoning per file naming the hunk that decided it. Then work out the blast radius: which modules import what the diff touched, and which test suites cover them. Emit a single JSON record on triage holding the per-file bands with their reasons, the blast radius, and the list of suites to run. Triage at most sixty files; if the diff is larger, take the sixty that touch the most call sites and state in the record how many you left out.in full above

model

claude-sonnet-5

agent

Triager

skill

skills/diff-triager.md

tools

Git

mcp

git

params

max_files: 60, temperature: 0.2

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs

pull_request : json

outputs

triage : json

dependencies

pr-intake

cannot

no type is refused

will_not

push to the repository it reads

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers

none

notes31 words

Read scope on the repository only, the triager clones and diffs, it never pushes. The write scope this line needs lives on merge-executor, at the far end of the human gate.

The card's own version, and who wrote it.

version

1.0.0

author

autogen

provenance

not stated