Tighten review prompt to suppress style nits#39
Merged
benlangfeld merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
Style/formatting/convention comments are now a hard prohibition rather
than "avoid," with reasoning that the reviewer hasn't read the repo's
linter/formatter config. Adds a phrase-level filter ("not a bug," "just
noting," "unconventional," etc.), redefines `low` as a minor real bug
rather than a place for observations, and extends the failure-mode
requirement to all severities.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
mkbaker
approved these changes
Apr 28, 2026
eabousaif
approved these changes
Apr 28, 2026
garettarrowood
approved these changes
Apr 28, 2026
drborges
approved these changes
Apr 29, 2026
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
6 participants
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
prompts/review.md: style/formatting/convention comments become a hard prohibition (with reasoning that the reviewer hasn't read the linter config),lowis redefined as a minor real bug rather than a place for observations, and every comment at every severity now requires a named failure mode.Test plan
lowfindings still surface with a stated failure mode.🤖 Generated with Claude Code