gh-create-pr

Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.

Quality

86%

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

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

A highly actionable, well-sequenced PR-creation workflow with strong validation checkpoints, held back mainly by redundancy across its three sections and a long inline ruleset that could be externalized. No bundle files are present, so structure is judged on the single-file organization.

Suggestions

De-duplicate the Workflow, Constraints, and Command Pattern sections — the push step, the 'show body before creating' rule, and the full bash sequence each recur; consolidate so each idea lives in one place.

Extract the elaborate base-branch / hotfix-title / bilingual release-note rules into a referenced file (e.g. references/branch-and-release-rules.md) and keep SKILL.md as a lean overview, improving progressive disclosure.

Tighten step 4's nested sub-bullets, which overlap (e.g. release-branch sourcing appears in multiple conditions); merge related conditions to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence with no concept over-explanation, but the Workflow, Constraints, and Command Pattern sections repeat each other (the push step, 'never create before showing', and the full bash sequence all appear more than once), so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready commands (`gh pr create --base --head --title --body-file`, the heredoc temp-file pattern) plus exact formats for hotfix titles and the bilingual release-note block, covering the common cases concretely.	5 / 5
Workflow Clarity	A clearly sequenced 9-step workflow with an explicit confirmation checkpoint (step 6) and a post-creation verify-and-fix feedback loop (step 7: verify the classifier added `hotfix`, else fix the title), supplemented by a Constraints checklist.	5 / 5
Progressive Disclosure	Well-organized into Workflow/Constraints/Command Pattern sections with clear headers, but at ~98 lines with no external reference files, the dense base-branch/hotfix/release-note ruleset is inlined rather than split into a one-level-deep reference.	4 / 5
	Total	17 / 20 Passed

Description

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

A strong, specific, third-person description that clearly states both capability and trigger conditions for a well-scoped PR-creation skill. Trigger-term coverage is good but bounded by the narrow single-domain subject matter.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create or update GitHub pull requests', 'reads `.github/pull_request_template.md`', 'fills every template section', 'preserves markdown structure exactly', 'marks missing data as N/A or None' — giving comprehensive, third-person coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (create/update PRs via the repository-required template workflow) and 'when' with concrete trigger phrasing ('Use when asked to create/open/update a PR').	5 / 5
Trigger Term Quality	Includes natural synonyms users would say ('create/open/update a PR', 'pull requests', 'PR'), but the single narrow domain offers no file extensions or broader term variations, so it sits below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — repo-specific template/backport/hotfix PR workflow with distinct triggers — making overlap with unrelated skills minimal.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: CherryHQ/cherry-studio
Path: .agents/skills/gh-create-pr/SKILL.md
Commit: 1219558

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.