create-pr

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/create-pr/SKILL.md

Quality

Content

75%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.

The body is a well-structured, actionable PR-creation workflow with executable commands and clear sequencing plus validation for presubmit. It is concise and uses appropriate cross-skill references, with minor room to trim redundancy and tighten validation guidance for merge/creation failures.

Suggestions

Trim redundancy: the "You must run cargo fmt and cargo clippy before" list largely restates the presubmit section; consolidate to one statement.

Add an explicit validation/feedback step for merge conflicts after "git merge origin/master" (resolve -> re-run presubmit) to complete the error-recovery loop.

Replace remaining placeholders (e.g., <base-branch>, "Title", "Description") with concrete example values or note how to derive them to push actionability toward copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with direct commands and minimal concept explanation, but retains some redundancy (repeated "You must run cargo fmt and cargo clippy" emphasis and "This helps you" bullet lists) that could be trimmed, fitting anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready commands (git fetch, ./script/presubmit, gh pr create/view/edit) plus a Rust layout-test template, but uses unfilled placeholders like <base-branch> and <title>, fitting anchor 4 rather than the fully ready anchor 5.	4 / 5
Workflow Clarity	The numbered Pre-PR Checklist (steps 1-6) is clearly sequenced with validation checkpoints (presubmit run, gh pr view exit-code check, fix-errors retry loop), but verification is concentrated on presubmit while merge-conflict and PR-creation failure recovery are less explicit, fitting anchor 4.	4 / 5
Progressive Disclosure	Content is organized into clear sections and delegates detail to related skills (write-pr-description, fix-errors, warp-integration-test) rather than inlining it, but some inlined detail (e.g., the full testing requirements) could be further delegated, fitting anchor 4.	4 / 5
	Total	16 / 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.

The description is well-constructed: it clearly states the skill's purpose and provides explicit, natural trigger phrases for when to invoke it. It is scoped to a distinct niche with low conflict risk, though the capability list could enumerate a few more concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain (PR creation in the warp repository) and one concrete action (create a PR for the current branch), but does not enumerate multiple distinct actions, matching anchor 3 rather than the several-actions anchor 4.	3 / 5
Completeness	Explicitly answers both what ("Create a pull request in the warp repository for the current branch") and when ("Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge") with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Covers several natural phrases users would say ("opening a PR", "creating a pull request", "submitting changes for review", "preparing code for merge"), but a few common variants are missing, fitting anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to the warp repository with a clear PR-creation niche and distinct triggers, giving minimal conflict risk with other skills, matching anchor 5.	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: warpdotdev/common-skills
Path: .agents/skills/create-pr/SKILL.md
Commit: b811c24

Reviewed: ~4 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.