prp-pr

Create a PR from current branch with unpushed commits. Use when the user wants to open or create a pull request, push and PR a branch, or invokes /prp-pr.

Quality

83%

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

77%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced PR-creation workflow with strong validation checkpoints. Its main weaknesses are verbosity from repeated checkpoint boilerplate and a lack of file-based progressive disclosure for a skill this size.

Suggestions

Consolidate the six PHASE_X_CHECKPOINT blocks into a single end-of-skill checklist or trim them to reduce repeated boilerplate and save tokens.

Move the default PR body template and the Handling Edge Cases section into a referenced file (e.g. references/pr-template.md) so SKILL.md stays a lean overview with one-level-deep navigation.

Tighten soft prose like the "Golden Rule" line into a terse, directive sentence that still conveys intent.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient git/gh commands and tables, but at ~330 lines it includes repeated PHASE_X_CHECKPOINT blocks and soft filler like the "Golden Rule" that could be trimmed without losing actionability.	2 / 3
Actionability	It provides fully executable bash and `gh` commands, concrete decision trees, a copy-paste-ready PR body template, and specific prefix tables — copy-paste ready guidance throughout.	3 / 3
Workflow Clarity	Phases 0–6 are clearly sequenced with an explicit VALIDATE phase, a decision tree, and checkbox PHASE_X_CHECKPOINT lists that act as validation checkpoints with error-recovery guidance.	3 / 3
Progressive Disclosure	The skill is a single ~330-line file with well-organized phase sections but no bundle files and no one-level-deep references; material such as the default PR template and edge cases is inline rather than split into separate files.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 clear, third-person description that explicitly pairs a concrete action with explicit trigger guidance and distinct invocation cues. The only weakness is that it describes essentially one action rather than enumerating multiple specific capabilities.

Dimension	Reasoning	Score
Specificity	"Create a PR from current branch with unpushed commits" names the domain and a concrete action, but it centers on a single main action rather than listing multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	It explicitly answers what ("Create a PR from current branch with unpushed commits") and when ("Use when the user wants to open or create a pull request, push and PR a branch, or invokes /prp-pr."), satisfying both halves.	3 / 3
Trigger Term Quality	"open or create a pull request, push and PR a branch, or invokes /prp-pr" covers the natural phrasings a user would actually say when needing this skill, including the slash-command invocation.	3 / 3
Distinctiveness Conflict Risk	The PR-creation niche is narrow with distinct triggers ("/prp-pr", "push and PR a branch") that are unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Wirasm/prp
Path: .claude/skills/prp-pr/SKILL.md
Commit: 1142738

Reviewed: 11 days 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.