Process PR
Process a GitHub PR as a maintainer, routing review, following revisions, checking merge readiness and reconciling linked Issues. Use for PR lifecycle management; use review-pr for technical review and fix-pr for author-side repairs.
Install
npx skills add hw-native-sys/simpler --skill process-prgit clone --depth 1 https://github.com/hw-native-sys/simpler.git /tmp/simpler
mkdir -p ~/.claude/skills
cp -r /tmp/simpler/.claude/skills/process-pr ~/.claude/skills/process-prPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Process a PR as maintainer Accept a PR number or URL, or an explicitly scoped set of PRs. Take the next justified action from its current state. The PR author owns delivery; reviewers review it. Do not require a PR assignee or use the committer as its owner. When called by [maintainer](../maintainer/SKILL.md), preserve its selected write scope, authority and observation context. Linked items outside that scope remain read-only; return the result to the caller without starting another maintenance loop. Developers may use this workflow for their own scope without acquiring maintainer permissions or taking over other contributors' work. ## Establish scope and authority Use [GitHub setup](../../lib/github/setup.md). Read the PR body, author, base and head SHA, draft/state, requested reviews, checks and mergeability. Read linked Issues and agreed design, plus all three feedback surfaces via [fetch-comments](../../lib/github/fetch-comments.md): inline threads, review summaries and conversation comments. Paginate when needed. Check current main and related open/draft PRs for duplicates, dependencies and integration conflicts. A small self-contained PR may carry its own goal without a separate Issue. A linked PR is delivery under its Issue, not a duplicate task. Respect actual authority and scope. An analysis/review request does not authorize publication or merging. A request to manage the PR may authorize routine routing
Details
- Skill name
process-pr- Repository
- hw-native-sys/simpler
- Path
.claude/skills/process-pr/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Process PR skill do?
Process a GitHub PR as a maintainer, routing review, following revisions, checking merge readiness and reconciling linked Issues. Use for PR lifecycle management; use review-pr for technical review and fix-pr for author-side repairs.
How do I install the Process PR skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill process-pr. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Process PR popular?
It lives in hw-native-sys/simpler, which has 49 GitHub stars and 102 forks.
Related skills
Benchmark
49hw-native-sys/simpler
Benchmark runtime performance on hardware. If the current branch has commits ahead of upstream/main or uncommitted changes, compares against the fork point (merge-base). Otherwise benchmarks current state only. Use when the user asks to benchmark, measure performance, or compare latency.
Checkout PR
49hw-native-sys/simpler
Add a remote for a given PR's head repository and checkout a local pr-xxx-work branch. Use when the user wants to work on someone else's PR locally.
Clean Branches
49hw-native-sys/simpler
Remove stale local and remote git branches that have been merged into main. Detects regular merges and squash merges. Cleans up fork remote branches and prunes tracking refs. Use when the user asks to clean up branches, remove merged branches, or tidy up git.
Review PR
49hw-native-sys/simpler
Review a GitHub PR or a fixed commit range from its background, existing pain points, and expected benefits through correctness, architecture, decoupling, performance, code quality, and repository standards. Uses the correct diff (fixed range or merge-base) and checks claims against implementation and evidence. Optionally folds in independent reviews from local `codex` / `claude` CLIs or read-only sub-agents when the invocation explicitly opts in. Use when the user asks to review a PR, a fixed range, or changes.
Process Issue
49hw-native-sys/simpler
Process a GitHub Issue as a maintainer, from triage and ownership routing through dependencies and evidence-based closure. Use to manage an Issue's next step; use fix-issue for implementation.
Vicious Mockery
113Hmbown/Wizards-of-the-Ghosts
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.