yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

1.10x

Quality

88%

Does it follow best practices?

Impact

99%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

A well-structured, highly actionable workflow with strong validation checkpoints, weakened mainly by some cross-section redundancy and a large block of PR-body guidance that lives inline rather than in a referenced file. No bundle reference files are present to support progressive disclosure.

Suggestions

Deduplicate template handling: describe template discovery once and have the Workflow section reference it, and consolidate the branch-to-PR inference so it appears in only one place.

Move the PR Title convention examples and the PR Body Contents guidance into a separate reference file (e.g. references/pr-body.md) and link to it from the main body, improving both conciseness and progressive disclosure.

Tighten the overlapping "explain why" / "explain what" / "net change" guidance in PR Body Contents into a single concise directive to reduce token cost.

Dimension	Reasoning	Score
Conciseness	Largely lean command snippets with no concept-explaining padding, but template handling is restated across "PR template discovery", "Workflow", and "PR Body Contents", and the branch-to-PR inference is repeated between "Workflow" and "Determining the PR" — content that could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (e.g. `git checkout -b`, `git add -A`, `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --template "$template"`) with concrete flags and env guards.	3 / 3
Workflow Clarity	Multi-step flow is clearly sequenced with explicit validation checkpoints (`gh --version`, `gh auth status`, checks rerun once, push-retry on auth errors, PR-existence check before creation) and error-recovery feedback loops.	3 / 3
Progressive Disclosure	Sections are well-organized with no nested references, but the substantial PR-body-authoring guidance (PR Title conventions, PR Body Contents, Suggested PR Body Shape) is inlined reference-style material that would be more navigable split into a reference file, and no reference bundle exists to offload it.	2 / 3
	Total	10 / 12 Passed

Description

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.

A tight, well-scoped description that states concrete actions and an explicit, restrictive trigger, making it both complete and clearly distinct from related git skills. Third-person voice is maintained and there is no fluff or over-claiming.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — "stage, commit, push, and open a GitHub pull request" — covering the domain comprehensively, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (stage/commit/push/open PR via gh) and when ("Use only when the user explicitly asks to ... in one flow"), satisfying the explicit-trigger anchor for both halves.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ("commit", "push", "open a GitHub pull request", "GitHub CLI (`gh`)") with good coverage and a natural "Use only when the user explicitly asks" trigger.	3 / 3
Distinctiveness Conflict Risk	The "only when ... in one flow" guardrail carves a distinct niche unlikely to collide with separate commit- or push-only skills.	3 / 3
	Total	12 / 12 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: openai/skills
Commit: 49f948f

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