address-github-pr-comments
npx machina-cli add skill gologo13/agent-skills/address-github-pr-comments --openclawAddress GitHub PR Comments
Overview
Process outstanding reviewer feedback, apply required fixes, and draft clear responses for each GitHub pull-request comment.
Steps
- Sync and audit comments
- Pull the latest branch changes
- Open the PR conversation view and read every unresolved comment
- Group comments by affected files or themes
- Plan resolutions
- List the requested code edits for each thread
- Identify clarifications or additional context you must provide
- Note any dependencies or blockers before implementing changes
- Implement fixes
- Apply targeted updates addressing one comment thread at a time
- Run relevant tests or linters after impactful changes
- Stage changes with commits that reference the addressed feedback
- Draft responses
- Summarize the action taken or reasoning provided for each comment
- Link to commits or lines when clarification helps reviewers verify
- Highlight any remaining questions or follow-up needs
Response Checklist
- All reviewer comments acknowledged
- Required code changes implemented and tested
- Clarifying explanations prepared for nuanced threads
- Follow-up items documented or escalated
- PR status updated for reviewers
Source
git clone https://github.com/gologo13/agent-skills/blob/main/skills/address-github-pr-comments/SKILL.mdView on GitHub Overview
Address GitHub PR Comments helps you process unresolved reviewer feedback, implement the required fixes, and draft clear responses for every PR comment. It keeps changes traceable by linking commits or lines and supports reviewers' verification. Following this process accelerates PR closure while maintaining code quality.
How This Skill Works
You first sync and audit all unresolved comments by pulling the latest changes and grouping feedback by file or theme. Then you plan resolutions, listing the required edits, clarifications, and any blockers. Next you implement fixes one thread at a time, run relevant tests or linters, and draft responses that summarize actions and link to commits or lines. Finally, you use the response checklist to confirm all comments are acknowledged and update the PR status as needed.
When to Use It
- When a PR has unresolved comments from reviewers after initial discussion
- When feedback spans multiple files or themes and requires planning before edits
- After implementing fixes, to draft clear, referenceable responses with links to commits/lines
- When dependencies or blockers require clarifications or additional context
- When you need to update PR status and document follow-up needs
Quick Start
- Step 1: Sync the branch, pull latest changes, and read every unresolved PR comment.
- Step 2: Plan resolutions by listing edits, clarifications, and blockers for each thread.
- Step 3: Implement fixes, run tests/linters, commit with references, and draft responses linking commits/lines.
Best Practices
- Audit all unresolved comments and group them by affected file or theme
- Plan resolutions by listing required edits, clarifications, and blockers
- Implement fixes per thread, and run relevant tests or linters
- Draft responses that reference commits or specific lines to aid verification
- Use the response checklist and document any follow-ups or status updates
Example Use Cases
- A PR has eight unresolved comments across two files; you audit, plan per-thread changes, implement fixes, run tests, and provide per-comment responses with links to the exact commits.
- Reviewer requests enhanced input validation; you plan edits, implement changes, add unit tests, and reference the commits in the draft response.
- Multiple lint warnings across modules; you group issues by file, fix style nits, and respond with a concise summary linking changes.
- A blocking dependency exists on another PR; you document the blocker and propose a workaround in the final response.
- After changes, you update the PR status and outline remaining follow-ups to close the PR.
