GitHub Review Follow-up
SkillDev toolsThis skill helps your AI turn GitHub pull request review feedback into finished fixes. It reads the review comments that are still unresolved, groups them into changes to make, and applies the ones you pick in your local code. It only replies to reviewers or marks threads resolved after you say to.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, ask your AI to look at the review comments on a pull request. It will show you the grouped fixes and wait for you to choose which ones to apply.
Then ask your AI: use the GitHub Review Follow-up skill
What your AI can do with it
- Read unresolved review comments on GitHub pull requests
- Group reviewer feedback into a clear list of fixes
- Apply the fixes you choose to your local code
- Reply to reviewers or resolve threads only when you explicitly ask
What this skill tells your AI
The instructions your AI receives, as published by devin-axis/ipollowork in examples/plugin-packages/github/skills/github-review-follow-up/SKILL.md and read by ahel’s review.
Use this skill for requested changes, inline review comments, and unresolved Pull Request feedback.
Workflow
- Resolve
owner,repo, and PR number from the request, URL, or current branch. - Call the GitHub service
pull-request-detailandreview-threadsactions. - Separate the returned threads into:
- unresolved and actionable;
- informational or approval-only;
- outdated, resolved, duplicate, or ambiguous.
- Group actionable items by file or behavior and present a numbered, concise scope.
- If the user asked to address everything, fix all clear unresolved items. Otherwise confirm which numbered items are in scope.
- Modify the local checkout with each change traceable to its review thread.
- Run the narrowest relevant tests and summarize what was addressed and what remains.
Write safety
- Do not post a comment or call
resolve-review-threadunless the user explicitly asks. - Never mark a thread resolved before the corresponding change or explanation is complete.
- If comments conflict or would regress behavior, explain the conflict before editing.
- If the PR or repository is ambiguous, stop and request the missing target rather than guessing.
Signals
- GitHub stars
- 6k
- Forks
- 1k
- Last commit
- Sep 2026
ahel review
S4info
community integration — published by devin-axis, not github
Automated review, not a security audit. Ruleset v1.
Advanced
- Catalog kind
- skill
- Gateway key
github-review-follow-up- Source
- github.com/devin-axis/ipollowork