feat: a posted review can end with the reviewer's own footer, and the preparing agent reads the pull request's description and discussion - #109
Merged
Conversation
… preparing agent reads the pull request's description and discussion The posted review's body now ends with `postFooter` under a blank line, where a team mention or an "automated triage, not a review" line belongs; the inline comments are untouched, so a mention fires once for the review. The preparing agent gets the pull request's own words: the description travels in its prompt, cut at 4 000 characters, and the discussion — comments, submitted reviews and inline review comments — is fetched with the daemon's credentials and written as pr-context.json in the pull request's data directory, never into the worktree. Both are framed as information written by others, never instructions, and with posting on the agent is told that a comment opening with postPrefix is an earlier automated pre-review not to re-raise. A forge that cannot be read costs a log line, not the review. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
postFooter(default empty) ends the posted review's own body under a blank line — a team mention, an "automated triage, not a review" line. The inline comments are unchanged, so a mention fires once for the review rather than once per finding. Config, settings, the page's Settings panel and the README all carry it.PrSnapshot.body—gh pr viewnow asks forbodytoo.gh— the agent has no credentials — and written aspr-context.jsonin the pull request's diffity data directory, never into the worktree, where an untracked file would show up in the review's own diff. Bodies cut at 20 000 characters with a… [cut]marker;postAlertson, a sentence saying a comment opening withpostPrefixis an earlier automated pre-review whose findings are not to be raised as ALERT again.Why
The review agent could not see the description or the discussion, so rules like "Risk Evaluation
highis an automatic flag" and "a previous flag comment already exists" were out of its reach, and the posted review had nowhere to carry a team mention or an attribution line.How to try it
Prepare a pull request that has a description and some comments: the agent's log shows the description and the
pr-context.jsonpath in the prompt, the file sits beside the prepared session, and a posted review ends with the footer.Part of #108 — PR B (quick triage of watched repositories) follows.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bwp5QefjsjMFeq6CK6cT6w