Extend review-agent phrasing rule to all finding severities#53
Merged
Conversation
Member
Author
Review SummaryVerdict: APPROVE FindingsNo issues found. Code looks correct and follows project conventions. The phrasing rule is consistently extended to CRITICAL findings in both the source skill (skills/review-agent.md) and the generated .claude/review-agent-prompt.md, and the regenerated hash matches between the two files. |
sebastientaggart
added a commit
that referenced
this pull request
Apr 8, 2026
…rule Extend review-agent phrasing rule to all finding severities
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
1 participant
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.
Extends the review-agent phrasing rule so CRITICAL findings — not just WARNING and NOTE — must be written as self-contained, standalone-title sentences. This ensures advisory-mode follow-up issues promoted from CRITICAL findings inherit the same usable-title guarantee.
Issue #51