How do I install the Gh Pr Description skill?

Run npx skillmds add vercel-eve/gh-pr-description in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Gh Pr Description skill do?

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. It is listed under Coding & Dev Tools on SkillMD.

Is Gh Pr Description safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Pr Description?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Pr Description free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Pr Description?

vercel (@vercel-eve) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Pr Description by vercel-eve — Agent Skill

Name: Gh Pr Description
Rating: 4.2 (5 reviews)
Author: vercel

File contents

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/pull_request_template.md. Write for a reviewer, not a changelog:

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. Prefer short sentences; split independent points rather than combining them into a long sentence.
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.

Preserve the checklist and check only verified items.

Publish

Before publishing, confirm the Summary leads with why the change is needed. Write the body to a file, then pass it to gh pr create or gh pr edit with --body-file.

Frequently asked questions