pr-description

Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that already has an open PR, or when the user says /pr-description, "write the PR description", or "update the PR title". Don't use for commit messages, changelogs, or review comments.

Quality

93%

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

88%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 procedure skill with concrete commands, templates, and validation gates for a destructive/outward-facing operation. The only real weakness is minor rule repetition and the absence of any reference split for its length.

Suggestions

Consolidate the repeated 'Do not run gh pr create / gh pr edit; stop' phrasing into one stated rule referenced from each gate to reduce redundancy.

Consider moving the section markdown templates (Root cause, Possible alternatives, Public API change) and/or the Red flags table into a references/ file to better fit progressive disclosure at this length.

Tighten the Red flags table by removing rows that restate rules already enforced inline in the Procedure (e.g. the feat-gate and bugfix-pr rows).

Dimension	Reasoning	Score
Conciseness	Lean and directive throughout, assuming Claude's knowledge of git/gh with no concept padding; docked one point for repeated stop/don't-post instructions across the feat gate, fix gate, and red flags table that could be consolidated.	4 / 5
Actionability	Copy-paste-ready commands ('gh pr create --title "…" --body-file …', 'git diff base...HEAD', 'gh pr list --limit 15 …') and concrete markdown templates for Root cause, Possible alternatives, and Public API change sections cover the common cases.	5 / 5
Workflow Clarity	Clear six-step procedure (ground → classify → feat gate → title → body → post) with explicit HARD-GATE validation checkpoints and feedback loops ('stop and tell the user', 'wait until they add one') for an outward-facing posting operation.	5 / 5
Progressive Disclosure	Well-organized single file with clear section headers and no nested references, but at ~200 lines with no one-level-deep bundle references it does not fully meet the split-content 5 anchor or the <50-line simple-skill exception.	4 / 5
	Total	18 / 20 Passed

Description

95%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 tightly-scoped, trigger-rich description that explicitly states both capability and activation conditions while carving out negative scope. It is among the strongest examples of a use-when description.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'writing a pull request title or body', 'run gh pr create', 'git push on a branch that already has an open PR' — listing several specific actions with minor gaps versus a full capabilities inventory.	4 / 5
Completeness	Explicit 'Use when…' clause answers both what (write PR title/body) and when (multiple concrete triggers), and adds negative scope ('Don't use for commit messages, changelogs, or review comments').	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms — 'write the PR description', 'update the PR title', '/pr-description' — plus command contexts users actually invoke.	5 / 5
Distinctiveness Conflict Risk	Clear niche (PR title/body writing and posting) with explicit exclusions that minimize overlap with commit-message, changelog, and review-comment skills.	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: TanStack/ai
Path: .agents/skills/pr-description/SKILL.md
Commit: 7fb4a5f

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