Review pr comments
Skill kin0992/dev-toolkit/packages/skills/src/engineering/review-pr-comments
Platform Engineering toolkit: reusable GitHub Actions, AI Skills, and shared TypeScript configs.
npx -y skills add kin0992/dev-toolkit --skill review-pr-commentsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
**INTERACTIVE SKILL** - Evaluate every actionable comment in unresolved GitHub PR review threads, including agent comments. USE FOR: review unresolved PR comments, triage review threads, process Copilot feedback. DO NOT USE FOR: general PR comments, resolving threads, unapproved replies. INVOKES: gh CLI, including gh api GraphQL and REST calls.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.4 KB, as published. Nobody here has run it
Review unresolved PR comments
Instructions
- Read and follow the complete workflow and
ghcommands. - Process one PR and all actionable comments in its unresolved review threads; include bots, but exclude general PR conversation comments.
- Evaluate each comment against the diff and source context.
- Ask one question at a time. Record
Acceptwith+1,Deferwitheyes, andIgnorewith-1. Do not edit code merely because it was accepted. - Suggest possible answers. Post a reply only after exact-text and target approval; editing a draft is not approval.
- Never resolve threads or post general PR comments.
Requires an authenticated gh CLI. Use gh api graphql --paginate to collect
threads and comments, and gh api REST calls for reactions and approved replies.
gh auth status
Errors
Surface API, permission, and missing-context failures; never silently skip them.