create-pr

Create a pull request for the current branch. Handles uncommitted changes, generates a PR title matching the `[{modules}] {type}: {description}` format enforced by CI, and fills in the PR description template. Trigger: 'create pr', 'open pr', 'submit pr', 'make pr'.

Quality

95%

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

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

The body is an exemplary instruction-only skill: fully executable commands, a clearly sequenced workflow with explicit validation gates and stop conditions, and dense repo-specific detail with no filler. Its only structural weakness is that everything lives inline in one long SKILL.md with no bundle files, where a portion of the reference material (e.g., the module table) could be split out.

Suggestions

Consider moving the module-mapping table and type list into a references/ file (e.g. references/modules.md), keeping only the core rules inline, to shrink the always-loaded SKILL.md body.

The interaction principle paragraph could be condensed to one sentence, since tool-level permission prompts already imply most of it.

Dimension	Reasoning	Score
Conciseness	The body is command-dense with essentially no padding: it teaches nothing Claude already knows and spends its tokens exclusively on repo-specific knowledge (the module-mapping table, the CI title regex location, the draft-file convention, the interaction policy). Not 4: there is no over-explanation left to trim — even prose sections like "Do not reproduce the template from memory — it changes" justify their tokens with a failure mode.	5 / 5
Actionability	Every step is copy-paste executable: `git branch --show-current`, `gh pr view --json number,title,body`, `git push -u origin HEAD`, `tail -n +3 .pr-drafts/<branch-name>.md > /tmp/pr-body.md` with `--body-file`, plus a concrete filename convention and file format example. Not 4: common cases (new PR vs. existing PR, title vs. body extraction) are each covered with exact commands.	5 / 5
Workflow Clarity	The four-step sequence is explicit with real validation checkpoints and feedback loops: stop on `main`, "If `make quality` fails: stop and report errors", stop when no commits are ahead, and "A `risky` verdict stops the PR: report it and wait for the user". Not 4: validation is explicit at every risky point (quality gate, review gate, empty-branch guard) rather than having minor gaps.	5 / 5
Progressive Disclosure	No bundle files exist; the ~155-line body is well-sectioned (Interaction Principle, Steps, Common Pitfalls) and its external references (`.github/PULL_REQUEST_TEMPLATE.md`, `.github/workflows/check_pr_title.yml`) are clearly signaled and one level deep. Not 5: the content is a single monolithic inline file — the 17-row module-mapping table in particular is sizable enough that a split into a reference file could be argued, so structure is good rather than optimally split.	4 / 5
	Total	19 / 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.

The description is specific, complete, and distinct: it enumerates the concrete capabilities of the skill, states the CI-enforced title format it satisfies, and provides explicit natural-language trigger phrases. The only weakness is slightly thin trigger synonym coverage.

Suggestions

Add one or two common trigger variations such as "open a pull request" or "submit for review" to broaden natural phrasing coverage without adding vagueness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create a pull request for the current branch", "Handles uncommitted changes", "generates a PR title matching the `[{modules}] {type}: {description}` format enforced by CI", "fills in the PR description template" — covering the full PR-creation workflow comprehensively. Not 4: there are no minor gaps in coverage; every phase of the task is named.	5 / 5
Completeness	Explicitly answers both "what" (create PR, handle uncommitted changes, generate CI-compliant title, fill description template) and "when" via an explicit Trigger clause with concrete phrases. Not 4: the "when" is fully explicit rather than merely present-but-could-be-more-specific, matching the anchor that requires concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes four natural trigger phrases users would actually say: "'create pr', 'open pr', 'submit pr', 'make pr'". Not 5: common variations like "open a pull request" or the bare abbreviation "PR" are missing, so coverage is good but not exhaustive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — PR creation for the current branch — with distinct, unambiguous triggers that would not fire for related skills (reviewing, merging, or commenting on PRs). Not 4: overlap risk is minimal, not merely reduced.	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: ByteDance-Seed/VeOmni
Path: .agents/skills/create-pr/SKILL.md
Commit: 86c5ec1

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