Improve code-review-assist skill for clearer reviews#4424
Merged
Conversation
The review output was overwhelming — it jumped straight into detailed questions without establishing context, making it hard for reviewers to orient themselves conceptually before evaluating concerns. Session planning changes: - Only load PR metadata (not diffs) during planning to keep it fast - Default merged-PR lookback to 2 days instead of unbounded - Surface existing review activity and stacked PR relationships - Present PRs one at a time during the session Review structure changes: - Add Background section that maps owners to named responsibilities by reading the original files, not just the diff - Add Important Changes section that frames the diff as a conceptual delta on the ownership/responsibility map - Rename "Key Review Questions" to "Key Concerns" with conventional comment severity labels (blocker, suggestion, question, nitpick) - Replace "Things That Look Fine" with a Recommendation (approve, request changes, or skip) grounded in the concerns Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4424 +/- ##
==========================================
+ Coverage 69.49% 69.52% +0.03%
==========================================
Files 486 486
Lines 50017 50017
==========================================
+ Hits 34760 34776 +16
+ Misses 12574 12558 -16
Partials 2683 2683 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
rdimitrov
approved these changes
Mar 30, 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
2 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
The review output from the code-review-assist skill was overwhelming — it jumped straight into detailed questions without establishing context, making it hard for reviewers to orient themselves before evaluating concerns. These changes restructure the skill so reviewers build a mental model of the code before seeing concerns, and every concern communicates its severity clearly.
Type of change
Changes
.claude/skills/code-review-assist/SKILL.mdSession planning
Review structure
blocker:,suggestion:,question:,nitpick:)Test plan
/code-review-assistwithout arguments and verify session planning loads only metadata/code-review-assist <PR>and verify the Background section establishes owners/responsibilities before diving into changesDoes this introduce a user-facing change?
Review sessions now provide a structured conceptual ramp (summary → background → changes → concerns → recommendation) instead of jumping directly into detailed questions, making it easier to understand PRs before evaluating them.
Generated with Claude Code