create-pull-request

Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/create-pull-request/SKILL.md

Quality

Discovery

100%

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

This is a well-crafted skill description that hits all the key criteria. It provides specific actions, includes a clear 'Use when' clause with natural trigger terms, and is distinctly scoped to GitHub PR creation. The mention of the gh CLI tool and project conventions adds helpful specificity without being overly verbose.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: commit analysis, branch management, PR creation, and mentions the specific tool used (gh CLI). Also references project conventions.	3 / 3
Completeness	Clearly answers both 'what' (create GitHub PRs, handle commit analysis, branch management, PR creation via gh CLI) and 'when' (explicit 'Use when' clause with multiple trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'create a PR', 'submit changes for review', 'open a pull request', 'GitHub pull request'. These cover common phrasings well.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to GitHub pull request creation specifically, with distinct triggers like 'PR', 'pull request', 'submit changes for review'. Unlikely to conflict with general git or code review skills due to the specific PR creation focus and gh CLI mention.	3 / 3
	Total	12 / 12 Passed

Implementation

55%

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

The skill provides a thorough, well-sequenced workflow for creating GitHub PRs with excellent actionability—every step has concrete, executable commands. However, it is far too verbose for a skill file, spending significant tokens explaining concepts Claude already understands (conventional commits, atomic commits, draft PR purposes, good vs bad title examples). The content should be condensed to roughly 1/3 its current size by removing explanatory material and either extracting or eliminating sections like Git Best Practices and detailed title generation guidance.

Suggestions

Remove or drastically condense sections that explain concepts Claude already knows: 'Git Best Practices', 'Draft PR Decision' rationale, good/bad title examples, and explanations of conventional commits format.

Extract detailed guidance (title generation strategies, commit hygiene, error handling) into separate reference files and link to them from the main skill.

Reduce the PR title generation section to a concise rule: 'Use conventional commit format if project uses it, otherwise create a descriptive action-oriented title. Append issue number if found.'

Condense the prerequisites section—Claude doesn't need installation instructions for gh CLI or explanations of what authentication means; just list the check commands and failure actions.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It explains many things Claude already knows (what conventional commits are, what 'atomic commits' means, what draft PRs are for, basic git concepts). Sections like 'Git Best Practices' and 'Intelligent PR Title Generation' with good/bad examples are largely unnecessary for Claude. The 'Draft PR Decision' section explains when to use drafts in detail Claude can infer.	1 / 3
Actionability	The skill provides fully executable bash commands throughout (gh pr create, git log, git diff, gh auth status, etc.) with concrete flags and arguments. Commands are copy-paste ready and cover the full workflow from prerequisites to post-creation.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced with explicit validation checkpoints: prerequisite checks (gh installed, authenticated, clean working directory), checking for existing PRs before proceeding, gathering context, creating the PR, and post-creation verification. Includes decision points and error handling with feedback loops (e.g., if PR exists, if conflicts arise).	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files. All content is inline including detailed sections on git best practices, title generation strategies, and draft PR decision logic that could be separate references or omitted entirely. The skill would benefit greatly from splitting advanced guidance into separate files.	1 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: warpdotdev/oz-skills
Commit: 6c08c49

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