Summary
The current /address-review workflow leads to endless review cycles where fixes generate more review suggestions. We need the command to support a "fix what matters, merge, follow-up the rest" pattern with quick keystroke actions.
Proposed quick-action menu
After triage, present options like:
f — Fix must-fix items only, reply-skip everything else, mark merge-readyf+i — Fix must-fix items, create a follow-up GitHub issue for discuss items, reply-skip the restd — Discuss specific items further before decidingr — Reply to all skipped/discuss items with rationale, resolve threadsm — Merge as-is (no fixes, post follow-up issue for everything)
Users can combine: e.g. f+i then r7-9 to fix, create issue, and reply to specific skipped items.
Key improvements
- Default to merge-ready: After addressing must-fix items, the command should suggest merging rather than waiting for another review cycle
- Follow-up issue creation: One-keystroke option to bundle all discuss/deferred items into a tracked GitHub issue with full context
- Batch reply with rationale: Reply to multiple skipped items at once explaining why they were deferred
- Range syntax: Support
r7-9 to reply to items 7 through 9 in a single action
- Unified numbering: Number all items sequentially across categories so every item has a unique reference number
Problem this solves
Bot reviewers (CodeRabbit, Codex, etc.) generate many suggestions per review cycle. Fixing some generates new suggestions on the fixes. The current workflow treats every review comment as potentially blocking, creating a cycle that delays merging. The improved flow makes it easy to fix real issues, defer the rest to a tracked issue, and merge.
🤖 Generated with Claude Code
Summary
The current
/address-reviewworkflow leads to endless review cycles where fixes generate more review suggestions. We need the command to support a "fix what matters, merge, follow-up the rest" pattern with quick keystroke actions.Proposed quick-action menu
After triage, present options like:
f— Fix must-fix items only, reply-skip everything else, mark merge-readyf+i— Fix must-fix items, create a follow-up GitHub issue for discuss items, reply-skip the restd— Discuss specific items further before decidingr— Reply to all skipped/discuss items with rationale, resolve threadsm— Merge as-is (no fixes, post follow-up issue for everything)Users can combine: e.g.
f+ithenr7-9to fix, create issue, and reply to specific skipped items.Key improvements
r7-9to reply to items 7 through 9 in a single actionProblem this solves
Bot reviewers (CodeRabbit, Codex, etc.) generate many suggestions per review cycle. Fixing some generates new suggestions on the fixes. The current workflow treats every review comment as potentially blocking, creating a cycle that delays merging. The improved flow makes it easy to fix real issues, defer the rest to a tracked issue, and merge.
🤖 Generated with Claude Code