pr-description
From the author
Write a clear pull-request description that gets reviewed fast and merged with confidence, from a git diff, branch summary, or commit list. Use when opening a PR, summarizing a change for review, documenting code changes, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.
Install
npx skills add mohitagw15856/pm-claude-skills --skill pr-description -a claude-code
Installs to .claude/skills/pr-description/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- write-specanthropics/knowledge-work-pluginsWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.OfficialWriting★ 31K
- github-review-prfeiskyer/claude-code-settingsReview GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for local uncommitted changes — this skill only reviews pull requests on GitHub.Engineering★ 1.7K
- requesting-code-reviewforyourhealth111-pixel/Vibe-SkillsPrepare and request a code review after implementation or before merge by assembling scope, requirements, git range, and reviewer instructions.Engineering★ 3.7K
- make-pr-easy-to-reviewmichael-denyer/pstack-claudePrepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".Engineering★ 3.2K
- product-briefjeremylongshore/tons-of-skills-marketplaceStructured product brief and PRD creation assistant. Use when the user needs to create a product brief, PRD, or feature spec that defines what to build and why. Trigger with "product brief", "PRD", "spec", "feature doc", "write a brief", or "define this feature".Writing★ 2.9K
- doc-maintenancepaperclipai/paperclipAudit README, SPEC, and PRODUCT docs against recent git history for drift and make minimal PR-ready edits. Use when asked to review docs for accuracy, after major feature merges, or on a schedule.Writing★ 105.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in