New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prp PR

by Wirasm in Wirasm/prp

Creates and opens GitHub pull requests. An agent skill from Wirasm/prp.

MITAuto-check passedDevelopment

Install Prp PR

skills CLI
$ npx skills add Wirasm/prp --skill prp-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Wirasm/prp prp-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prp-pr .claude/skills/prp-pr && rm -rf skills-src

Use ~/.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/

Facts

Skill name
prp-pr
GitHub stars
2.3k
Token cost
~1.4k tokens
SKILL.md length
768 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Creates and opens GitHub pull requests. An agent skill from Wirasm/prp.

  • Works in 5 steps: Establish the PR target → Validate the committed work → Write the pull request → …
  • Creating a PR on GitHub
  • SKILL.md covers Scope, 1. Establish the PR target, 2. Validate the committed work and 3. Write the pull request, plus 2 more sections
  • Calls git and gh

What it does

Prp PR is an agent skill from Wirasm/prp. Creates and opens GitHub pull requests. Always use when creating a PR on GitHub, when the user explicitly asks to create or open a PR, when another PRP workflow reaches its PR-creation step, or when the user invokes $prp-pr.

Its SKILL.md is about 1.4k 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. It works with GitHub. The repository describes itself as: Prompts, workflows and more for agentic engineering. The licence is MIT.

When your agent uses it

  • Creating a PR on GitHub
  • The user explicitly asks to create
  • Another PRP workflow reaches its PR-creation step
  • The user invokes $prp-pr

Example prompts

  • “Use the prp-pr skill to create and opens GitHub pull requests. An agent skill from Wirasm/prp”
  • “/prp-pr”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Establish the PR target
  2. Validate the committed work
  3. Write the pull request
  4. Push and create
  5. Verify and report

What it can do on your machine

Read from SKILL.md and the folder at commit 4352925. 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:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and 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

Prp PR loads about 1.4k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 768 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 Wirasm/prp at commit 4352925, republished under its MIT licence (© Wirasm). 768 words, ~1,433 tokens.

Download SKILL.mdSave it as .claude/skills/prp-pr/SKILL.md (or your agent's skills folder).
name
prp-pr
description
Creates and opens GitHub pull requests. Always use when creating a PR on GitHub, when the user explicitly asks to create or open a PR, when another PRP workflow reaches its PR-creation step, or when the user invokes $prp-pr.

Arguments: $ARGUMENTS (and $1, $2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.

Create Pull Request

Create a clear, reviewer-friendly GitHub pull request for the completed work on the current branch.

Arguments: $ARGUMENTS

Scope

Run this at the PR-creation step after the requested work has been done by the current agent, a subagent, or another collaborator. Ensure every change belonging to that work is committed before opening the PR. If intended changes remain uncommitted, invoke $prp-commit with a natural-language target that identifies only those changes, then verify the resulting commit. Never sweep unrelated worktree changes into the commit.

The pull request itself is the artifact; do not create a separate local PR document.

1. Establish the PR target

Inspect the current branch, repository instructions, remote branches, and Git history. Determine the base in this order:

  1. An explicit --base <branch>.
  2. The base recorded on an existing PR for this branch.
  3. The repository's documented development flow.
  4. Branch ancestry against likely integration branches such as development, dev, and the remote default branch.
  5. The remote default branch as a fallback.

Use the same resolved base for every log, diff, and PR command. Never assume main. If the evidence is genuinely ambiguous, stop and ask rather than opening the PR against a guessed target.

Check whether any open or closed PR already exists for the current branch. If one exists, return its URL and state instead of creating a duplicate.

2. Validate the committed work

  • Re-read git status and the diff after any commit to confirm no intended changes were omitted.
  • Confirm the current branch is not the resolved base and contains commits ahead of it.
  • Fetch current remote state, then read the complete merge-base diff and commit range against the resolved base—not only the file list or diff stat.
  • Compare the diff with the user's requested outcome and repository instructions. Stop if the branch does not contain the intended work or includes unexplained scope.
  • Find the repository's pull request template in its supported root, .github, or docs locations. If several templates could apply and the correct one cannot be inferred, ask which to use.

3. Write the pull request

Treat repository rules as syntax constraints, not as the writing-quality standard. Write in plain, natural language. Cut filler, generic praise, formulaic transitions, and vague claims. Use the repository's exact terms and name concrete behavior and evidence.

Title
  • Write a concise, human-readable title describing the meaningful outcome.
  • Preserve enforced repository syntax such as required types, scopes, or issue identifiers.
  • Do not imitate vague or implementation-focused titles merely because they appear in repository history.
  • Use Conventional Commit style only when the repository requires or consistently uses it.

Bad: feat(core): add child run traversal and parent event aggregation

Good: feat(core): workflows can now include a child workflow in the parent run

Show full SKILL.md (285 more words)Show less
Description

Use the repository's pull request template whenever one exists. Preserve its structure and fill every applicable section with concrete information from the request, diff, commits, and validation evidence.

If no template exists, use this fallback:

markdown
## Problem

{Explain the original problem and why it matters to the user.}

## Solution

{Briefly explain how the change resolves it, focusing on behavior rather than an inventory of files and functions.}

## Validation

- `{actual command}` — passed
- {Concrete manual verification, when applicable}

{Fixes/Closes/Relates to #N when supported}
{Plan: <verified published-plan URL> when supplied}
  • Lead with the problem, then the solution. Do not lead with an implementation inventory.
  • Report only validation that actually ran. If none ran, say so and explain why; never add generic unchecked boxes as evidence.
  • Add Fixes or Closes only when the PR fully resolves the referenced issue. Use Relates to for a non-closing relationship. Do not infer issue linkage from an unexplained bare number.
  • When a verified published-plan URL is supplied, link it in the repository template's Links or planning context section. This is the reviewer-accessible implementation contract; never substitute a local plan path.
  • Never add AI attribution, a generated-by footer, a robot emoji, or Co-Authored-By: Claude.

4. Push and create

Push the current branch with upstream tracking when needed. If the remote branch has diverged or the push is rejected, stop and report the conflict; do not rebase or force-push as part of this skill.

Create a ready-for-review PR against the resolved base. Use --draft only when the user explicitly requests a draft. Pass the prepared title and body to gh pr create without opening an interactive editor.

5. Verify and report

Read the created PR back from GitHub and verify its number, URL, title, base, head, draft state, and open state. Check CI status without waiting for pending jobs.

Return the PR URL first, followed by the verified title, base <- head, ready/draft state, and current checks. Keep the report concise.

Do not report success until GitHub confirms the PR exists with the intended base and head.

© Wirasm, 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 .agents/skills/prp-pr of Wirasm/prp.

Open the folder on GitHubat commit 4352925

Compare with similar skills

Prp PR 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.

Prp PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prp PR this skillWirasm/prp2.3k—~1.4kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

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.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from Wirasm/prp

All 37 skills in this repo

  • PRP Loop

    Wirasm/prp

    Runs the plan, implement and review pipeline detached in fresh headless sessions, looping review and fix until the pull request is clean.

    2.3k GitHub stars~894 tokensUpdated 6 days ago
    Auto-check passed

  • PRP Loop: Autonomous Pipeline

    Wirasm/prp

    Runs a detached, resumable loop that plans, implements, opens a PR, reviews and fixes a feature across headless CLI sessions until the review is clean.

    2.3k GitHub stars~863 tokensUpdated 6 days ago
    Auto-check passed

  • PRP Workstream Orchestrator

    Wirasm/prp

    Coordinates several PRP workstreams in isolated Git worktrees from one session, verifying proof, holding merge gates and sequencing the merges.

    2.3k GitHub stars~3.5k tokensUpdated 6 days ago
    Auto-check passed

  • PRP Implementation Planner

    Wirasm/prp

    Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.

    2.3k GitHub stars~4.1k tokensUpdated 6 days ago
    Auto-check passed

  • PRP Plan

    Wirasm/prp

    Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.

    2.3k GitHub stars~4k tokensUpdated 6 days ago
    Auto-check passed

  • PRP Spike

    Wirasm/prp

    Settles a feasibility question with the smallest throwaway build that could disprove it, in an isolated worktree, ending in a verdict backed by evidence instead of a PR.

    2.3k GitHub stars~3.8k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Prp PR

What does Prp PR do?

Creates and opens GitHub pull requests. An agent skill from Wirasm/prp. Prp PR is an agent skill from Wirasm/prp. Creates and opens GitHub pull requests.

When should I use Prp PR?

Prp PR fits situations like: creating a PR on GitHub; the user explicitly asks to create; another PRP workflow reaches its PR-creation step; the user invokes $prp-pr.

How do I install Prp PR in Claude Code?

Run `npx skills add Wirasm/prp --skill prp-pr -a claude-code`. Or copy the skill folder (.agents/skills/prp-pr in Wirasm/prp) into .claude/skills/prp-pr in your project. Claude Code loads it when a task matches its description.

How do I install Prp PR in Codex?

Run `npx skills add Wirasm/prp --skill prp-pr -a codex`. Or copy the skill folder (.agents/skills/prp-pr in Wirasm/prp) into .agents/skills/prp-pr in your project. Codex loads it when a task matches its description.

Can I use Prp PR 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 Wirasm/prp --skill prp-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prp-pr, .gemini/skills/prp-pr, .github/skills/prp-pr and .opencode/skills/prp-pr in your project.

What does Prp PR need to run?

Going by SKILL.md and its folder, Prp PR needs the command-line tools its instructions call (git and gh).

Does Prp PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prp PR 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 Prp PR use?

Prp PR 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 Prp PR use?

About 1.4k tokens (SKILL.md is roughly 5.7k 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 Prp PR?

Skills that share tags, products or a category with Prp PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prp PR?

Wirasm (a GitHub user) maintains it in Wirasm/prp, which has 2,259 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.

Source: Wirasm/prp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.