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.
Install with Tessl CLI
npx tessl i github:warpdotdev/oz-skills --skill create-pull-request89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels across all dimensions. It clearly states what the skill does (create GitHub PRs with commit analysis and branch management), explicitly defines when to use it with natural trigger terms, and is distinctive enough to avoid conflicts with other skills. The description uses proper third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'commit analysis, branch management, and PR creation using the gh CLI tool'. Also mentions 'following project conventions' which adds specificity about how it operates. | 3 / 3 |
Completeness | Clearly answers both what ('Create a GitHub pull request', 'Handles commit analysis, branch management, and PR creation') AND when ('Use when the user asks to create a PR, submit changes for review, or open a pull request') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'create a PR', 'submit changes for review', 'open a pull request', 'GitHub pull request'. These cover common variations of how users request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub PR creation with distinct triggers like 'PR', 'pull request', 'submit changes for review'. The mention of 'gh CLI tool' further distinguishes it from general git or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and comprehensive coverage of the PR creation process. The main weaknesses are moderate verbosity (explaining concepts Claude already knows, like what draft PRs are for) and a monolithic structure that could benefit from progressive disclosure through external references for detailed subsections.
Suggestions
Remove explanatory text about what draft PRs are for and when to use them - Claude understands this; just provide the decision criteria as a brief list
Move the 'Intelligent PR Title Generation' section with conventional commits examples to a separate CONVENTIONS.md file and reference it
Trim the installation instructions for gh CLI to just the command or a single link - Claude doesn't need step-by-step installation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as explaining what to do if gh CLI is not installed (Claude can figure this out) and overly detailed explanations of when to use draft PRs. Some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific gh CLI syntax, git commands, and clear copy-paste ready examples. Every step has concrete commands to run. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing, explicit validation checkpoints (prerequisites check, existing PR check, clean working directory), and decision points with clear branching logic (draft vs regular PR, rebase scenarios). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document that could benefit from splitting detailed sections (like conventional commits format, error handling) into separate reference files. No external file references are used. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
93%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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 16 Passed | |
- 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.