github-pr-description

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.

Quality

82%

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

65%Weight 40%Scale 1-3

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

An actionable, well-sequenced skill with real commands and concrete examples, but it is a verbose monolith: duplicated anti-pattern lists, five full examples, and no external reference files or error-recovery guidance for PR creation. Trimming redundancy and externalizing examples would lift the weaker dimensions.

Suggestions

De-duplicate the anti-patterns: keep a single "What to Avoid" list and remove the repeated "Anti-Patterns to Avoid" in the Notes section to improve conciseness.

Add an error-recovery feedback loop for `gh pr create` (e.g., what to do on auth failure, an existing open PR for the branch, or network errors) to raise workflow clarity.

Move the five worked PR-description examples into a referenced `references/examples.md` file and keep only one or two inline, turning the monolith into a lean overview with one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	The workflow steps are command-based and free of basic-concept padding, but the anti-patterns list is duplicated ("What to Avoid" and "Anti-Patterns to Avoid") and five full worked examples (~140 lines) could be trimmed to two or three — efficient overall but with redundant and padded sections.	2 / 3
Actionability	Provides fully executable commands (e.g. "git log origin/main..HEAD --oneline", "gh pr create --title ... --body-file .forge/FORGE_PR_DESCRIPTION.md") plus concrete copy-paste-ready PR description examples, matching the score-3 anchor.	3 / 3
Workflow Clarity	A clear 6-step sequence with an explicit prerequisite check (Step 1), but no error-recovery/feedback loop for the fragile gh pr create step (auth, network, or existing-PR failures), so it sits at the score-2 "sequence present but checkpoints missing or implicit" level rather than 3.	2 / 3
Progressive Disclosure	Well-organized with clear section headers, but it is a ~345-line monolith with no bundle files or external references, and the ~140 lines of inline worked examples are content that should be split into a separate file — matching the score-2 "content that should be separate is inline" anchor rather than a split, navigable score-3.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description with explicit "Use when..." triggers, multiple concrete capabilities, and a distinct PR-related niche. Minor fluff ("comprehensive, meaningful") is present but does not undermine specificity or trigger quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Generate and create pull request descriptions automatically using GitHub CLI" and "Analyzes git diff and commit history" — matching the score-3 anchor of multiple specific concrete actions rather than the single-domain score-2 example.	3 / 3
Completeness	Explicitly answers both what (generate/create PR descriptions via gh, analyzing diff and history) and when via an explicit "Use when..." clause, exactly matching the score-3 anchor; the trigger clause is present so it is not capped at 2.	3 / 3
Trigger Term Quality	Covers natural phrases users would say — "create a PR", "generate a PR description", "make a pull request", "submit changes for review" — giving good trigger coverage; not reduced to 2 because it goes well beyond the single-variation "Works with PDF files" anchor.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (PR description creation via GitHub CLI) with distinct triggers unlikely to fire for unrelated skills; the mild fluff ("comprehensive, meaningful") does not rise to a conflict or over-claim that would drop it to 2.	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: tailcallhq/forgecode
Path: crates/forge_repo/src/skills/github-pr-description/SKILL.md
Commit: 1ca089a

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.