Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Review PR comments, analyze validity, and create action items
Install Review PR Comments
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pheuter/svelte-check-rs review-pr-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review-pr-comments .claude/skills/review-pr-comments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .claude/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-commentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pheuter/svelte-check-rs review-pr-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/review-pr-comments .agents/skills/review-pr-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .agents/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pheuter/svelte-check-rs review-pr-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/review-pr-comments .cursor/skills/review-pr-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .cursor/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pheuter/svelte-check-rs.git --path .claude/skills/review-pr-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pheuter/svelte-check-rs review-pr-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/review-pr-comments .gemini/skills/review-pr-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .gemini/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pheuter/svelte-check-rs review-pr-commentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/review-pr-comments .github/skills/review-pr-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .github/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pheuter/svelte-check-rs review-pr-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pheuter/svelte-check-rs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/review-pr-comments .opencode/skills/review-pr-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-pr-comments" agent skill from https://github.com/pheuter/svelte-check-rs/tree/main/.claude/skills/review-pr-comments into .opencode/skills/review-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-pr-comments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-pr-comments- GitHub stars
- 135
- Token cost
- ~1k tokens
- SKILL.md length
- 431 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review PR comments, analyze validity, and create action items
- Works in 7 steps: Filter Comments → Analyze Each Comment → Decide: Address or Decline → …
- Tasks that involve Pull requests
- SKILL.md covers PR Context, Workflow, Response Tone and Reply Commands
- Calls gh
What it does
Review PR Comments is an agent skill from pheuter/svelte-check-rs. Review PR comments, analyze validity, and create action items
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: Sunsetted / archived. Rust Svelte 5 checker (Jan–Sep 2026) that helped inspire upstream native checking. Use official svelte-check; see README. The licence is MIT.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/review-pr-comments”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 134a25f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review PR Comments loads about 1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 431 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pheuter/svelte-check-rs at commit 134a25f, republished under its MIT licence (© pheuter). 431 words, ~1,033 tokens.
Download SKILL.mdSave it as
.claude/skills/review-pr-comments/SKILL.md (or your agent's skills folder).- name
- review-pr-comments
- description
- Review PR comments, analyze validity, and create action items
Review pull request comments on the current branch's PR. Determine which to address in code and which to decline with a polite response.
PR Context
PR Info
!gh pr view --json number,title,url,headRepository,headRepositoryOwner,author,state,baseRefName,headRefName --jq '{number, title, url, repo: .headRepository.name, owner: .headRepositoryOwner.login, author: .author.login, state, base: .baseRefName, head: .headRefName}'
Review Threads
!read -r OWNER REPO NUMBER <<< "$(gh pr view --json number,headRepository,headRepositoryOwner --jq '"\(.headRepositoryOwner.login) \(.headRepository.name) \(.number)"')" && gh api graphql -f query="query { repository(owner: \"$OWNER\", name: \"$REPO\") { pullRequest(number: $NUMBER) { reviewThreads(first: 100) { nodes { id isResolved isOutdated path line comments(first: 50) { nodes { id databaseId body author { login } createdAt } } } } } } }" --jq ".data.repository.pullRequest.reviewThreads.nodes[] | {thread_id: .id, resolved: .isResolved, outdated: .isOutdated, path: .path, line: .line, comments: [.comments.nodes[] | {id: .databaseId, author: .author.login, body, created_at: .createdAt}]}"
Top-Level Comments
!gh pr view --json comments --jq '.comments[] | {type: "top-level", id, author: .author.login, body, createdAt}'
Changed Files
!gh pr diff --name-only
Workflow
1. Filter Comments
Skip:
- Resolved threads (
resolved: true) — unless user asks to review them - Deployment bot comments (vercel, etc.)
- Comments already replied to by the PR author
- Purely informational comments with no action requested
Prioritize human reviewers over bot comments. Note outdated threads but still analyze them.
2. Analyze Each Comment
For each open, actionable comment:
- Read the code at the referenced file and line (with surrounding context)
- Understand the ask — bug fix, style, architecture, performance, testing, docs, etc.
- Research if needed — check for similar patterns, conventions (CLAUDE.md), related code
3. Decide: Address or Decline
Address if it identifies a bug, security issue, missing error handling, convention violation, or aligns with existing patterns.
Decline if it's over-engineering, out of scope, personal preference, premature optimization, or conflicts with project conventions.
Borderline cases — use AskUserQuestion to let the user decide.
Show full SKILL.md (155 more words)Show less
4. Create Tasks
One task per actionable comment using TaskCreate:
- Code changes: Subject
"Fix: {description}", include comment quote, author, file:line, specific action, andmetadata: {comment_id, action: "code_change"} - Responses: Subject
"Reply: {topic}", include comment quote, reasoning, draft reply, andmetadata: {comment_id, action: "respond"}
5. Summary
Show TaskList, then a summary table:
| Comment | Author | File | Decision | Task | Reason |
|---|---|---|---|---|---|
| Brief description | @user | path:line | Address/Decline | #id | Short reason |
Mention any resolved/skipped threads briefly below the table.
6. Get Direction
Use AskUserQuestion with these options:
- Make code changes — implement changes for "Address" items
- Post responses — reply on GitHub for "Decline" items
- Both — code changes and responses
- Review only — no action
7. Execute
Work through tasks: mark in_progress, execute, mark completed. Ask for clarification if anything is unclear.
Response Tone
Write replies as a teammate — conversational, direct, concise. Acknowledge valid points even when declining. Explain the "why", reference specific code or constraints. No formulaic openers. Match the reviewer's formality.
Reply Commands
# Reply to review thread comment
gh api --method POST repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="Your reply"
# Reply to top-level comment
gh api --method POST repos/{owner}/{repo}/issues/{number}/comments -f body="@username Your reply"© pheuter, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/review-pr-comments of pheuter/svelte-check-rs.
Open the folder on GitHubat commit 134a25f
Compare with similar skills
Review PR Comments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review PR Comments this skillpheuter/svelte-check-rs | 135 | — | ~1k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from pheuter/svelte-check-rs
Commit
pheuter/svelte-check-rs
Review current changes, commit, push, and optionally open a PR
Related
Categories
Questions about Review PR Comments
What does Review PR Comments do?
Review PR comments, analyze validity, and create action items. Review PR Comments is an agent skill from pheuter/svelte-check-rs.
When should I use Review PR Comments?
Review PR Comments fits situations like: tasks that involve Pull requests.
How do I install Review PR Comments in Claude Code?
Run `npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a claude-code`. Or copy the skill folder (.claude/skills/review-pr-comments in pheuter/svelte-check-rs) into .claude/skills/review-pr-comments in your project. Claude Code loads it when a task matches its description.
How do I install Review PR Comments in Codex?
Run `npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a codex`. Or copy the skill folder (.claude/skills/review-pr-comments in pheuter/svelte-check-rs) into .agents/skills/review-pr-comments in your project. Codex loads it when a task matches its description.
Can I use Review PR Comments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pheuter/svelte-check-rs --skill review-pr-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr-comments, .gemini/skills/review-pr-comments, .github/skills/review-pr-comments and .opencode/skills/review-pr-comments in your project.
What does Review PR Comments need to run?
Going by SKILL.md and its folder, Review PR Comments needs the command-line tools its instructions call (gh).
Does Review PR Comments access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Review PR Comments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Review PR Comments use?
Review PR Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review PR Comments use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Review PR Comments?
Skills that share tags, products or a category with Review PR Comments: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review PR Comments?
pheuter (a GitHub user) maintains it in pheuter/svelte-check-rs, which has 135 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 5, 2026.
Source: pheuter/svelte-check-rs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.