PR Make Suggestion Edit
Review the current PR comprehensively and make suggestion edits to improve code quality, without committing or pushing changes.
Review Process
Step 1: Understand Current PR Context
First, gather context about the current PR:
- Check current branch:
git branch --show-current - View PR details:
gh pr view - See what changes are in this PR:
git diff main...HEAD(or appropriate base branch) - Review recent commits:
git log --oneline -10
Step 2: Run Comprehensive Reviews in Parallel
Run these two reviews simultaneously:
- Code-Reviewer Subagent Review (Primary Focus)
- Use Task tool with
subagent_type: "code-reviewer" - Focus on structure, patterns, performance, accessibility, type safety, readability
- Codex Review (Secondary - cross-model security/correctness check)
- Invoke
/code-review(the built-in reviewer; add-co→/deep-reviewwhen a cross-model second pass is wanted) - Focus on the critical security and correctness issues it surfaces
Step 3: Analyze and Categorize Findings
Categorize findings by type and priority:
- Structural improvements
- Code quality
- Performance
- Accessibility
- Type safety
- Security
- Bug fixes
- Style/Formatting
Step 4: Present Findings to User
Present a clear, organized summary and ask for approval before making edits.
Step 5: Apply Suggestion Edits
After user approval:
- Make edits systematically - Go through each suggested change
- Group changes by topic - Keep related changes together
- Leave changes UNSTAGED - Do NOT add, commit, or push anything
- Track what was done - Keep a mental note of which topics were addressed
After making edits, show git status and diff.
Important Rules
CRITICAL - DO NOT:
- Do NOT run
git add - Do NOT run
git commit - Do NOT run
git push - Do NOT stage any files
DO:
- Make edits using Edit tool
- Group edits by logical topics
- Leave all changes unstaged
- Clearly communicate what was changed and why
- Show git diff summary at the end
Notes
- This command focuses on making suggestion edits that improve the existing PR
- Changes should be constructive and actionable
- Group changes by logical topics for easier PR creation later
- All changes remain unstaged for the next command to handle
- The companion command
/pr-make-suggestion-to-prwill create PRs from these edits