create-pr

Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull_request_template.md, --body formatting, codex/ branch names, and Codex app git directives.

Quality

95%

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

92%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 tight, executable PR-creation playbook with a well-sequenced workflow, real validation and error-recovery feedback loops, and clean sectioning. Its only weakness is mild verbosity in the PR Body guidance paragraphs.

Suggestions

Tighten the PR Body prose: merge the 'what'/'why'/'verification' guidance into a compact checklist rather than four separate explanatory paragraphs.

Replace the placeholder `<paths>`/`<branch>`/`<body>` tokens with a one-line note on how to derive them, or link to an example, so the commands are fully self-sufficient.

Consider pulling the detailed fork-vs-branch policy into a referenced file if it grows, keeping the inline summary to preserve the current one-level reference depth.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable commands and minimal over-explanation, but the PR Body section carries several prose paragraphs ('A why should be included...', 'Omitting the why should be used sparingly...', 'Do not include trivial verification commands...') that could be tightened without losing clarity.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — git status/switch/add/commit/push and `gh pr create --draft --base canary --head <branch> ...` — plus a concrete PR body template and recovery commands covering the common cases.	5 / 5
Workflow Clarity	A clearly numbered 5-step sequence with an explicit validation checkpoint (`git diff --cached --check`), pre-mutation state inspection, and a Recovery section providing feedback loops (lock/permission errors → escalate, network failure → escalate, approval denied → report, duplicate → `gh pr view` check).	5 / 5
Progressive Disclosure	Well-organized into clear sections (Fork vs Branch PRs, Workflow, PR Body, Recovery, Related Skills) with a single one-level-deep, clearly-signaled external reference ('See ... in `AGENTS.md` for the full policy') and no nested references; content is appropriately self-contained for this scope.	5 / 5
	Total	19 / 20 Passed

Description

100%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 specific, trigger-rich, and clearly niched to the Next.js + Codex PR workflow, explicitly answering both what the skill does and when to invoke it. It is concise yet comprehensive with no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create Git branches, commits, pushes, and GitHub pull requests') plus specific sub-tasks ('recover from gh pr create / PR template issues', '--body formatting, codex/ branch names'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ('Create Git branches, commits, pushes, and GitHub pull requests for Next.js') and when ('Use when the user asks to create a branch, commit current changes, open a PR or draft PR...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are comprehensively covered with synonyms — 'create a branch', 'commit current changes', 'open a PR or draft PR', 'publish a pull request' — matching how a user would actually request this skill.	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche ('for Next.js', 'codex/ branch names', 'Codex app git directives', '--base canary') with distinct triggers, making conflict with generic git/PR skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: vercel/next.js
Path: .agents/skills/create-pr/SKILL.md
Commit: 1119ce6

Reviewed: 8 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.