pr-reviewlisted

# PR Review Skill Reviews all open PR comment threads one at a time. For each comment, Claude proposes its verdict and reasoning, waits for your approval, then replies and resolves. ## Bundled Scripts All GitHub API interactions go through these scripts — never call `gh api` directly or use shell redirects: - `pr_review_parse_comments.sh <owner/repo> <pr_number>` — list all unresolved threads - `pr_review_parse_comments.sh <owner/repo> <pr_number> <index>` — full detail by 1-based index including replies - `pr_review_parse_comments.sh <owner/repo> <pr_number> --id <comment_id>` — full detail by comment database ID - `pr_review_post_reply.sh <owner/repo> <pr_number> <comment_id> "<reply text>"` — posts a reply to a comment thread - `pr_review_resolve_thread.sh <thread_node_id>` — resolves a review thread by its GraphQL node ID They ship in this skill's `bin/` directory, which is on the Bash tool's `PATH` whenever the skill is installed. **Invoke each by bare name** — never by an absolute path. The bare form is the only spelling that works on both install routes, and it is what the permission rules match. The `pr_review_` prefix is deliberate: these rules approve a command *name*, so a generic one like `post_reply` could be satisfied by an unrelated executable earlier on `PATH`. The matching rules live in the toolkit's `project-files/.claude/settings.json` template and are **not installed by either install route** — the user merges them in. If every call prompts, that is