review-pr: harden Pre-Verdict Audit against comment-quality halo effect - #68
Draft
warp-agent-staging[bot] wants to merge 1 commit into
Draft
Conversation
Require enumerating each comment individually (file:line) during the Pre-Verdict Audit so none get skimmed past as part of a holistic impression, and explicitly forbid treating a comment's writing quality, technical accuracy, or the importance of the issue it describes as a mitigating factor when checking it against the repository's commenting guidelines (or, absent guidelines, the existing commenting distribution in the project). Co-Authored-By: Warp Agent <agent@warp.dev>
Contributor
Author
|
This PR was generated with Warp. |
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.


Summary
Hardens the
## Pre-Verdict Auditsection of.agents/skills/review-pr/SKILL.mdagainst a "comment-quality halo effect": a reviewer judged a comment as fine because it was well-written and explained a genuinely hard bug, and let that impression substitute for actually checking it against the target repo's commenting guidelines — missing confirmed rule violations as a result.Changes
Verification
git diff origin/eval-base/019ff1e1touches exactly one file,.agents/skills/review-pr/SKILL.md, with a single line replaced (1 insertion, 1 deletion) — the Comments bullet under## Pre-Verdict Audit. No other lines, trailing whitespace, or line endings changed.Co-Authored-By: Warp Agent agent@warp.dev