CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tight, command-driven PR-creation workflow with executable examples, explicit per-phase validation checkpoints, and good error-recovery guidance. It fully respects Claude's competence and stays self-contained without padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what a PR or git is — relying on commands and decision tables; every section earns its place.

3 / 3

Actionability

It provides fully executable git and gh commands plus a complete, copy-paste-ready heredoc PR-body template and a concrete output report block.

3 / 3

Workflow Clarity

A clearly sequenced 7-phase (0–6) flow with explicit PHASE_N_CHECKPOINT checklists, a STOP/WARN/PROCEED decision tree, and a verify phase including gh pr checks.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a self-contained single file with no external references; per the rubric's simple-skills note, its well-organized phase sections qualify for the top score.

3 / 3

Total

12

/

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 well-constructed description that pairs a concrete capability statement with an explicit 'Use when' trigger clause and natural user phrasings. The only weakness is moderate specificity — it names a single core action rather than enumerating several.

Suggestions

Broaden the capability list to a few concrete sub-actions (e.g., "create a PR, fill in PR templates, and link related issues") to lift specificity toward the top anchor.

DimensionReasoningScore

Specificity

"Create a PR from current branch with unpushed commits" names a concrete domain and one main action with a clear scope condition, but does not list multiple distinct actions like the score-3 anchor.

2 / 3

Completeness

It answers both 'what' ("Create a PR from current branch with unpushed commits") and 'when' via an explicit "Use when..." clause.

3 / 3

Trigger Term Quality

"open or create a pull request, push and PR a branch, or invokes $prp-pr" covers several natural phrasings a user would actually say, plus the slash-command trigger.

3 / 3

Distinctiveness Conflict Risk

It carves a clear PR-creation niche with a dedicated $prp-pr slash-command trigger, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Wirasm/prp
Reviewed

Table of Contents

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.