How do I install the Pr Description skill?

Run npx skillmds@latest add basicmachines-co-basic-memory/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.

Is 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 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 Pr Description free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pr Description?

basicmachines-co (@basicmachines-co-basic-memory) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Description by basicmachines-co-basic-memory

Name: Pr Description
Rating: 4.2 (5 reviews)
Author: basicmachines-co

File contents

PR Description Writer

Create and publish high-quality PR descriptions that help reviewers understand intent, implementation details, and verification steps.

When to Use

Opening a new PR
Refreshing a stale or minimal PR description
Capturing implementation rationale for future debugging

Goals

Every PR body should clearly answer:

What changed?
Why did we make this change now?
How was it implemented?
How was it tested?
What risks or follow-ups remain?

Workflow

Discover PR context and changed files.
Extract intent from commit(s) and code changes.
Draft a structured PR body.
Apply the body to the PR.
Re-open the PR view and confirm body/labels.

Commands

# Identify the active PR for current branch
gh pr view --json number,title,url,baseRefName,headRefName

# Inspect changed files and patch summary
gh pr diff --name-only
gh pr diff

# Review commit messages for intent
git log --oneline --decorate -n 10

# Apply updated body
gh pr edit <pr-number> --body-file /tmp/pr-body.md

Body Structure

Use the template in references/pr-body-template.md.

Required sections:

## Why
## What Changed
## Implementation Details
## Testing
## Risks / Follow-ups

Quality Bar

Be specific: name concrete files, routes, scripts, and commands.
Explain tradeoffs and constraints, not just mechanics.
Testing section must include exact commands run and outcomes.
If something is not tested, state it explicitly.

Optional Enhancements

Add ## Screenshots for UI work.
Add ## Rollout Notes when release sequencing matters.
Add ## Reviewer Guide for large diffs.

---name: pr-descriptiondescription: Use when opening or updating a GitHub PR - writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested.license: MIT--- # PR Description Writer Create and publish high-quality PR descriptions that help reviewers understand intent, implementation details, and verification steps. ## When to Use - Opening a new PR - Refreshing a stale or minimal PR description - Capturing implementation rationale for future debugging ## Goals Every PR body should clearly answer: 1. What changed? 2. Why did we make this change now? 3. How was it implemented? 4. How was it tested? 5. What risks or follow-ups remain? ## Workflow 1. Discover PR context and changed files. 2. Extract intent from commit(s) and code changes. 3. Draft a structured PR body. 4. Apply the body to the PR. 5. Re-open the PR view and confirm body/labels. ## Commands ```bash # Identify the active PR for current branch gh pr view --json number,title,url,baseRefName,headRefName # Inspect changed files and patch summary gh pr diff --name-only gh pr diff # Review commit messages for intent git log --oneline --decorate -n 10 # Apply updated body gh pr edit <pr-number> --body-file /tmp/pr-body.md ``` ## Body Structure Use the template in [references/pr-body-template.md](references/pr-body-template.md). Required sections: - `## Why` - `## What Changed` - `## Implementation Details` - `## Testing` - `## Risks / Follow-ups` ## Quality Bar - Be specific: name concrete files, routes, scripts, and commands. - Explain tradeoffs and constraints, not just mechanics. - Testing section must include exact commands run and outcomes. - If something is not tested, state it explicitly. ## Optional Enhancements - Add `## Screenshots` for UI work. - Add `## Rollout Notes` when release sequencing matters. - Add `## Reviewer Guide` for large diffs.

Frequently asked questions

Pr Description