review template's goal statement asks pins of others' pull requests #153

Open
opened 2026-10-20 17:31:47 +02:00 by motoko · 0 comments
Collaborator

Location

  • .agents/templates/review.md, the Goal statement comment (lines
    16–20): the goal statement takes "the form the work template gives a
    Brief".
  • .agents/templates/work.md, the Constraints comment (lines 56–65): "a
    behavior no test guards first getting a pin, as AGENTS.md § Testing
    and verification names it".

Seen at 150d921.

Evidence

The review template sends review-pr to the work template's Brief for
the goal statement's form, and so to its Constraints comment. That
comment asks that a kept behavior no test guards first get a pin, a
committed test. review-pr reviews a pull request someone else opened
and commits nothing to it, so the pin cannot exist. The old form,
review-pr/review.md, borrowed the same comment, so this predates the
review template.

Scenario

An agent writes the goal statement for a pull request that keeps a
behavior no test guards. Following the Constraints comment, it either
stops to ask whether it should write a pin, or writes a constraint that
asks for one, and the reviewers then judge the pull request against a
pin nobody can add.

Smallest fix

In the review template's Goal statement comment, add: "Its Constraints
name the tests that guard each kept behavior, or that none does,
without pins."

## Location - `.agents/templates/review.md`, the Goal statement comment (lines 16–20): the goal statement takes "the form the work template gives a Brief". - `.agents/templates/work.md`, the Constraints comment (lines 56–65): "a behavior no test guards first getting a pin, as AGENTS.md § Testing and verification names it". Seen at 150d921. ## Evidence The review template sends `review-pr` to the work template's Brief for the goal statement's form, and so to its Constraints comment. That comment asks that a kept behavior no test guards first get a pin, a committed test. `review-pr` reviews a pull request someone else opened and commits nothing to it, so the pin cannot exist. The old form, `review-pr/review.md`, borrowed the same comment, so this predates the review template. ## Scenario An agent writes the goal statement for a pull request that keeps a behavior no test guards. Following the Constraints comment, it either stops to ask whether it should write a pin, or writes a constraint that asks for one, and the reviewers then judge the pull request against a pin nobody can add. ## Smallest fix In the review template's Goal statement comment, add: "Its Constraints name the tests that guard each kept behavior, or that none does, without pins."
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
claudiomaradonna/agent-foundry#153
No description provided.