review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers skill".
Profile →npx skills add dyoshikawa/rulesync --skill review-pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
target_pr = the user's request If target_pr is not provided, use the PR of the current branch. ## Important: Do Not Switch the Local Branch - Do NOT check out, switch, or otherwise move the local branch (e.g., `git checkout`, `git switch`, `gh pr checkout`). - To inspect the PR's changes, use `git` and `gh` commands that read remote state without moving the working tree. For example: - `gh pr view $target_pr` to read PR metadata and description. - `gh pr diff $target_pr` to read the diff. - `gh pr view $target_pr --json files` or `gh api` to list changed files. - `git fetch origin pull/<PR_NUMBER>/head:refs/remotes/origin/pr-<PR_NUMBER>` and `git diff origin/main...origin/pr-<PR_NUMBER>` if a local read-only ref is needed. - When invoking subagents, explicitly instruct them that switching the local branch is forbidden and that they must inspect changes via `git`/`gh` commands only. Execute the following in parallel: - Call code-reviewer subagent to review the code changes in $target_pr. Pass along the rule that the local branch must not be switched and that diffs must be obtained via `git`/`gh` commands. - Call security-reviewer subagent to review the security issues in $target_pr.
- Important: Do Not Switch the Local Branch
- Reporting Rules
- After the Review: Check GitHub Actions Workflows
What does the review-pr skill do?
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers skill".
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill review-pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.