create-pr
Creates a GitHub pull request for the current branch using the gh CLI. Use when asked to create a PR, open a pull request, submit changes for review, or push and create a PR. Defaults to draft, detects and fills repo PR templates, auto-detects the base branch, and supports 'ready for review' override. DO NOT TRIGGER for reviewing existing PRs or commenting on PRs.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 an excellent skill description that covers all dimensions thoroughly. It provides specific capabilities, natural trigger terms, explicit 'Use when' and 'DO NOT TRIGGER' clauses, and clearly carves out its niche distinct from related PR-reviewing skills. The description is concise yet comprehensive, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates a GitHub pull request, uses gh CLI, defaults to draft, detects and fills repo PR templates, auto-detects the base branch, and supports 'ready for review' override. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates a GitHub PR using gh CLI with draft default, template detection, base branch auto-detection) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios, plus explicit exclusion criteria). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create a PR', 'open a pull request', 'submit changes for review', 'push and create a PR'. Also includes negative triggers ('DO NOT TRIGGER for reviewing existing PRs or commenting on PRs') which helps disambiguation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (creating PRs specifically), and the explicit 'DO NOT TRIGGER' clause for reviewing/commenting on PRs actively prevents the most likely conflict with a PR review skill. | 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, actionable skill with clear sequential workflow and executable commands throughout. Its main weakness is moderate verbosity — the Common Mistakes section explains things Claude already understands, and the Draft Override section is partially redundant with Step 3. Overall it's a solid skill that effectively guides PR creation with appropriate defaults and validation.
Suggestions
Trim the 'Common Mistakes' section to just the non-obvious items (like dynamic base branch detection) and remove entries that restate what's already in the workflow steps.
Merge the 'Draft Override' section into Step 3 as a brief note rather than a separate section with redundant trigger phrases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary content. The 'Common Mistakes' section explains things Claude already knows (like 'vague titles tell reviewers nothing'), and the 'Draft Override' section repeats what was already stated in Step 3. The template detection ls commands could be more concise. | 2 / 3 |
Actionability | Fully executable bash commands throughout — gh CLI commands are copy-paste ready, branch detection logic is concrete, template detection uses real file paths, and the PR creation commands include actual flags. The fallback body template is specific and usable. | 3 / 3 |
Workflow Clarity | Clear sequential steps (prerequisites → template detection → PR creation) with explicit validation checkpoints: checking gh auth status, verifying branch is pushed before proceeding, detecting base branch dynamically. The conditional logic (template exists vs. not, draft vs. ready) is well-structured with clear decision points. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in a single file. The 'Integration' section at the bottom provides useful cross-references. However, the common mistakes section and draft override section add bulk that could be more tightly integrated or separated if the skill were part of a larger system. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- shousper/claude-kit
- Commit
a01bac9
- 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.