Get card
Download
review-drafter@1.0.0.yamlClone
npx -y darkprint clone review-drafter@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Turn the triage record into a review a maintainer can act on, one comment per finding, anchored to a file and a line, and fold the last test failure into the draft when the suite came back red.
used in 1 blueprint
Specification
146 words · handed to the agentYou are handed a triage record listing, per changed file, a risk band, the reasoning behind it, and the test suites the change is expected to move. Write a review a maintainer can act on: one comment per finding, each anchored to a file path and a line number, each stating what is wrong and what would fix it. Cover every file banded high before you write about anything else, and say nothing at all about files banded mechanical. A failures signal is attached only when the previous run of the suites came back red; when it is there, open the review with those failing cases and tie each one to the finding it belongs to. Emit the finished review as Markdown on review with at most twenty-five comments, and repeat the suite names the record selected so whoever runs them next knows what to execute.
Interfaces
2 in · 1 outInputs
2Outputs
1| Name | Data type | Description |
|---|---|---|
| review | markdown | The drafted review, findings anchored to files and lines, ready for the suite. |
Dependencies
2The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.
Card values
17 declaredWho the node is. The id is the key the DOT pins.
- id
- review-drafter
- name
- Review Drafter
- type
- agent
- phases
- Implementation
What it does, and the prose the agent is handed when the graph runs.
- action38 words
- Turn the triage record into a review a maintainer can act on, one comment per finding, anchored to a file and a line, and fold the last test failure into the draft when the suite came back red.
- spec146 words
- You are handed a triage record listing, per changed file, a risk band, the reasoning behind it, and the test suites the change is expected to move. Write a review a maintainer can act on: one comment per finding, each anchored to a file path and a line number, each stating what is wrong and what would fix it. Cover every file banded
highbefore you write about anything else, and say nothing at all about files bandedmechanical. Afailuressignal is attached only when the previous run of the suites came back red; when it is there, open the review with those failing cases and tie each one to the finding it belongs to. Emit the finished review as Markdown onreviewwith at most twenty-five comments, and repeat the suite names the record selected so whoever runs them next knows what to execute.in full above - model
- claude-sonnet-5
- agent
- Reviewer
- skill
- skills/review-drafter.md
- tools
- none
- mcp
- none
- params
- temperature: 0.3, max_comments: 25
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- triage : json, failures : status
- outputs
- review : markdown
- dependencies
- diff-triager, test-runner
- cannot
- no type is refused
- will_not
- write about a file banded mechanical
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes33 words
failuresis optional because the first pass has nothing to fold in: it is fed only by the red edge back from the test runner, which is what makes this pair a loop.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- review-drafter@1.0.0currentsha256:d8e653500e485283ac5bd232908fef0bacdeecccbf7c21484f7c92b7de7313c8
pinned byGuarded Merge Bot
autogen/guarded-merge-bot
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.