prp-pr

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly lean PR-creation workflow with strong sequencing and explicit validation/verification throughout. Minor improvements are possible in trimming rationale and providing a complete ready-to-run gh pr create example.

Suggestions

Tighten the base-resolution section by collapsing the repeated rationale into the ordered list to reduce redundancy.

Add a complete copy-paste `gh pr create` example (with --base, --title, --body, optional --draft) so the creation step is fully executable rather than described.

Consider extracting the fallback PR template into a reference file so the main body stays a lean overview, which would also strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no primers on what a PR or GitHub is), but a few elaborative sentences (e.g., the repeated base-resolution rationale) could be trimmed, placing it just below the every-token-earns-its-place anchor at 5.	4 / 5
Actionability	It gives concrete commands (gh pr create with --draft/--base, $prp-commit, git status) and bad/good title examples, but the final gh pr create invocation is described rather than given as a complete copy-paste example, leaving minor gaps versus the fully-executable anchor at 5.	4 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints and feedback loops (re-read git status after commit, fetch remote state, verify the created PR exists, do not report success until GitHub confirms) matches the clear-sequence-with-validation anchor.	5 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested or buried references, but at ~100 lines it exceeds the under-50-line simple-skill threshold, so it does not reach the clear-overview-with-one-level-references anchor at 5.	4 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that clearly answers both what the skill does and when to use it, with concrete natural-language triggers and a distinct niche. The only gap is limited action breadth and the lack of "pull request" spelled out among the trigger terms.

Dimension	Reasoning	Score
Specificity	"Creates and opens GitHub pull requests" names the domain and two concrete actions but offers no broader coverage of PR-related operations, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It explicitly states what the skill does ("Creates and opens GitHub pull requests") and gives multiple concrete "when" trigger clauses ("Always use when creating a PR on GitHub, when the user explicitly asks..."), satisfying the both-what-and-when anchor.	5 / 5
Trigger Term Quality	It includes natural phrases users would say ("creating a PR on GitHub", "create or open a PR") plus the invocation token, but does not spell out "pull request" or list synonyms/file extensions, so it falls short of comprehensive coverage at 5.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear niche (GitHub PR creation/opening) with distinct, specific triggers and the PRP-scoped invocation token, giving it minimal overlap with unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Wirasm/prp
Path: .agents/skills/prp-pr/SKILL.md
Commit: 9724799

Reviewed: ~12 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.