Agent skill · writing content · vercel
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
Why this skill is useful
Codifies a specific standard for drafting GitHub pull request descriptions that the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 4,425 stars on the source repository.
What this skill does
GitHub PR description Inspect the branch diff, commits, related issue or discussion, tests, docs, and changesets. When updating a PR, read its current body first. Write Fill in .github/pullrequesttemplate.md. Write for a reviewer, not a changelog: Follow these ASD-STE100 rules where they apply: Use approved words from the ASD-STE100 dictionary, with one meaning per word. Use active voice and keep one topic in each sentence. Limit descriptive sentences to 25 words and procedural sentences to 20 words. Keep necessary technical terms, proper nouns, and code identifiers. Keep the Summary to one short paragraph: usually 2–4 sentences and about 100 words or fewer. Lead with the concrete problem, user need, or decision behind the change; follow with the solution and meaningful behavior. Split independent points into separate sentences. Do not list files or narrate commits. Include implementation detail only when it is necessary to assess behavior or risk. Mention breaking changes, preserved behavior, tradeoffs, scope boundaries, follow-ups, or stacked PRs only when they matter to review. Link an existing issue or discussion with Closes #N, Related to #N, or an equivalent when one exists. Do not create an issue solely for a PR. State only validation that actually ran, including limitations or failures. In PR bodies, do not list routine checks like typecheck, lint, or standard test runs as "Test plan" items (those are implied engineering hygiene). This also applies to reviewer-facing suggestions such as "recommended before merge: run turbo typecheck test" or "run pnpm oxfmt-check on the edited files" — CI already runs these on every PR, so listing them is noise. Only call out a check in Validation if it exercises change-specific behavior that CI does not cover (e.g. a manual production probe, a dashboard spot-check, a one-off data query). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/gh-pr-description