| name | review-pr |
| description | Address a requested pull-request comment against the real code at the PR head. Read the thread, source, and covering test; reproduce behavioral claims in the right KIND-backed environment; apply only the minimum valid fix; prove it; then reply and resolve that thread. Trigger when the user asks to address or review a PR comment, a Greptile finding, or a named review thread. For a request covering several comments, repeat this narrow action for each one without combining their scopes.
|
/review-pr — address a PR comment
The authoritative procedure is Address a PR comment. Read it
before acting and keep the detail there.
The action is narrow:
- Identify the PR and requested comment.
- Read the PR head, complete thread, cited source, and covering test.
- Reproduce the claim against the right KIND-backed topology when practical.
- Adjudicate it as valid, invalid, or valid-but-not-worth-changing, with evidence.
- Apply only the valid comment's minimum fix and covering test.
- Run the affected gate and prove the changed behavior.
- Push, reply with the proof, and resolve only the handled thread.
- Report unrelated comments, CI failures, and branch state without changing them.
A reply is published, so it references planning by bare issue identifier (ENG-1234) — never a linear.app URL, an
issue title, or a project name. See Linking a PR to its Linear
issue.
For a dirty tree that needs a new PR, use create-pr. For a failed GitHub Action, use the separate failed-Action flow
in docs/agent-workflows.md.
