pull-requestfollow-uplisted

Follow up as the author on review feedback left on your own PR/MR: check which reviewer comments still need a response, investigate how threads were resolved (including silent resolves), and draft replies. With --auto, autonomously triage AI-reviewer (bot) threads and loop until the reviewer is satisfied, clearing a bot review hands-off. With --local, run the same bot loop pre-push through the reviewer's CLI (Greptile, CodeRabbit) against unmerged commits, before any PR exists. Use when reviewers commented on your PR and you need to respond or satisfy them. Use --local proactively, without being asked, whenever you are about to push or open a PR in a repo with a supported bot (bot config present, CLI installed). Triggers: "respond to review comments on my PR", "address reviewer feedback", "make the bot reviewer pass", "greptile review", "coderabbit review", "run the review bot locally", "bot review before pushing".
bendrucker/claude · ★ 15 · Code & Development · score 76

Install: claude install-skill bendrucker/claude

# PR Follow-Up Follow up on review feedback for: $ARGUMENTS Parse the URL and flags from `$ARGUMENTS`. GitHub URLs contain `github.com`; GitLab URLs contain the instance hostname. GitHub is primary: work through `gh`, `mcp__github`, and `github:*` skills directly. Delegate all GitLab behavior to `gitlab:merge-request` (no `glab` calls). - `--auto`: autonomously triage **bot** threads, looping until the reviewer is satisfied (see [The Autonomous Loop](#the-autonomous-loop)). - `--include-human-nits`: under `--auto`, also act on **human** threads, but only trivial high-confidence changes (typos, renames, one-liners). Off by default. - `--local [base]`: run the bot loop pre-push through the reviewer's CLI instead of PR threads, against the branch's unmerged commits (see [Local Mode](#local-mode-pre-push)). The optional base overrides what the review runs against. No PR is involved, so `pr-url` and the other flags don't apply. ## Default Workflow (Gated) Without `--auto`, stay read-only: fetch, classify, draft, **check with me before posting or resolving**. Fetch all resolvable threads (resolved and unresolved) via `github:pr-comments` (`--role author`) or `gitlab:merge-request`, then classify: - **Unresolved / no reply** - **Unresolved / replied** - **Resolved / with reply** - **Resolved / silent**: resolved with no author reply; flag these, they hide context For unresolved threads, diff the comment's creation date against HEAD to see whether later commits addressed the