Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From review
Follows up on reviewed PRs/MRs: fetches and classifies review threads (unresolved, replied, silent resolves), checks commit coverage, summarizes status, suggests approve/re-review/comment.
npx claudepluginhub bendrucker/claude --plugin reviewHow this skill is triggered — by the user, by Claude, or both
Slash command
/review:follow-upThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow up on my review of: $ARGUMENTS
Follows up on GitHub/GitLab PR/MR review threads: classifies unresolved/replied/resolved/silent states, checks commit coverage for fixes, drafts replies. Use for checking feedback responses or thread resolutions.
Fetches and filters PR review comments, extracts outside-diff-range feedback from review bodies, and resolves threads with proper attribution. Useful when addressing CodeRabbit, Cursor, or human reviewer feedback.
Fetches GitHub PR review threads and top-level comments including resolved ones, synthesizes into asked/done/outstanding buckets, generates per-thread action plans with grouped commits. Supports --focus and --resolve flags.
Share bugs, ideas, or general feedback.
Follow up on my review of: $ARGUMENTS
Parse the URL from $ARGUMENTS to determine the platform. GitHub URLs contain github.com, GitLab URLs contain the GitLab instance hostname.
Load the gitlab:api and gitlab:merge-request skills for API patterns and MR tooling.
Gather all resolvable discussion threads that I started (both resolved and unresolved).
Use the github:pr-comments skill's script to fetch threads. Run with --role reviewer to get threads started by the authenticated user. For resolved threads, use the GraphQL API via gh api graphql to query pullRequest.reviewThreads, filtering to threads where the first comment author matches the viewer.
Get the authenticated username, then use the gitlab:merge-request skill's discussions.ts script to fetch threads:
glab api user --jq .username 2>/dev/null
bun <gitlab:merge-request skill>/scripts/discussions.ts list <iid> --resolvable --author <username>
Include both resolved and unresolved threads (do not pass --unresolved) for classification.
When making direct glab api calls, append 2>/dev/null to prevent config warnings from polluting JSON output.
Sort each thread into one of four buckets:
Show a table with counts per category. List each thread with the file, line, one-line summary of my original feedback, and whether the author replied.
For each thread, examine commits pushed after my review submission. Indicate which threads appear addressed by code changes vs. which have no corresponding changes.
Help decide next action based on thread states:
After I decide on next steps, use platform-appropriate commands:
gh pr review --approvegh pr commentgh api graphql with resolveReviewThread mutationglab api projects/:id/merge_requests/<iid>/approve -X POST 2>/dev/nullglab api projects/:id/merge_requests/<iid>/discussions/<id> -X PUT -f resolved=true 2>/dev/null-f resolved=falsegitlab:merge-request skill's discussions.ts create command