โ† ClaudeAtlas

workflow-pr-reviewlisted

Use when reviewing a remote GitHub PR โ€” fetches into an ephemeral worktree, runs the reviewer agent with a Review Decision footer instruction, deduplicates findings against existing review threads (ยฑ5-line fuzzy match + Jaccard โ‰ฅ 0.4 against any author), posts new inline comments via gh-api, adds ๐Ÿ‘ reactions on dedup matches, and submits the review with APPROVE or COMMENT. Counterpart of local-diff review (which workflow-development Phase 4 keeps using).
lugassawan/swe-workbench ยท โ˜… 2 ยท Code & Development ยท score 71
Install: claude install-skill lugassawan/swe-workbench
# Workflow: PR Review (remote-PR orchestration shell) **Announce at start:** "I'm using the workflow-pr-review skill to review PR #N." ## When to invoke - The user passes a PR number to `/swe-workbench:review` (e.g. `/review 123`). - The user accepts the auto-detect prompt on `/review` no-arg ("Detected PR #N โ€” review it? Reply `yes`"). - An agent or command needs to "review this remote PR end-to-end" โ€” fetch + analyse + post + submit. - Phrases: "review PR 123", "do a peer review of #456", "fetch this PR and post deduped comments". ## When NOT to invoke - Local-diff review (working tree / staged / branch diff) โ†’ use `commands/review.md` no-arg directly. The command stays the entrypoint for local-diff mode. - `workflow-development` Phase 4 โ†’ keeps using local-diff review (no remote PR exists yet during implementation). - The user wants to post a single comment without running a full review โ†’ out of scope. - The PR is closed/merged โ†’ out of scope; reviews target open PRs. ## Composition This skill orchestrates; analysis is delegated to: - `swe-workbench:reviewer` subagent โ€” produces `Severity | File:Line | Issue | Why | Fix` findings + a Review Decision footer (when instructed by this skill โ€” see Step 4). - `swe-workbench:ticket-context` skill โ€” prepended to the reviewer prompt when the PR body or commit messages reference a ticket key, atlassian/Confluence URL, or `#NNN` GitHub ref. - **Checkpoint:** write the workflow state file (see `docs/workflow-state.md`) at each