pr

Creates a draft GitHub pull request with a plain-text conventional-commit title and a succinct description of the branch. Use when the user asks to open, raise, or create a pull request or PR.

Quality

90%

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

93%Scale 1-5

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

This is an excellent skill that is lean, actionable, and well-structured. It provides concrete examples for both titles and PR bodies, includes exact CLI commands, and handles edge cases (missing template, missing gh CLI). The only minor gap is the lack of an explicit post-creation verification step in the workflow.

Dimension	Reasoning	Score
Conciseness	Every section earns its place. No explanation of what a PR is, what conventional commits are conceptually, or how git works. The content is dense with actionable specifics and zero padding.	5 / 5
Actionability	Provides exact commands (gh pr create with flags), concrete title examples, a complete default body template, and a realistic example body. The common actions section adds copy-paste ready commands for follow-up tasks.	5 / 5
Workflow Clarity	The four-step workflow is clearly sequenced with validation as step 1 (auth status, branch check, uncommitted changes). However, there's no explicit validation checkpoint after PR creation (e.g., verify the PR was created successfully, check the URL) and no feedback loop for handling creation failures beyond the error handling section.	4 / 5
Progressive Disclosure	For a skill of this size and scope, the content is well-organized into logical sections (workflow, title rules, body rules, common actions, error handling) with appropriate depth. No bundle files are needed, and no content is over-inlined or buried.	5 / 5
	Total	19 / 20 Passed

Description

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

This is a strong skill description that clearly communicates what the skill does (creates draft GitHub PRs with conventional-commit titles) and when to use it (when users ask to open/raise/create a PR). The description is concise, uses third person voice, and includes good trigger terms. Minor improvements could include additional synonym coverage for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: creates a draft PR, uses plain-text conventional-commit title, and generates a succinct description of the branch. Minor gaps—doesn't mention things like assigning reviewers, adding labels, or targeting specific base branches.	4 / 5
Completeness	Clearly answers both 'what' (creates a draft GitHub PR with conventional-commit title and succinct description) and 'when' (explicit 'Use when' clause with concrete trigger phrases like 'open, raise, or create a pull request or PR').	5 / 5
Trigger Term Quality	Includes strong natural trigger terms: 'pull request', 'PR', 'open', 'raise', 'create', and 'GitHub'. Missing some variations like 'merge request', 'submit PR', or 'push a PR'.	4 / 5
Distinctiveness Conflict Risk	Highly distinct—specifically targets GitHub draft pull request creation with conventional-commit formatting. Unlikely to conflict with other skills like commit message generation, code review, or general git operations.	5 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: rikdc/ai-skills
Path: plugins/git-workflow/skills/pr/SKILL.md
Commit: a43676e

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