How do I install the Pr Description skill?

Run npx skillmds@latest add bernardorubin/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 Pr Description skill do?

Use when the user asks to generate, write, draft, or update a pull request description on GitHub. Triggers on phrases like "write a PR description", "draft the PR body", "update the PR description", "fill in the PR", or "generate description for PR ". Operates on the current branch's PR by default, or one specified by number/URL. Updates the PR directly via `gh pr edit`, falls back to ~/Desktop/pr-description.md if the GitHub update fails. It is listed under Coding & Dev Tools on SkillMD.

Is Pr Description safe to use?

This skill has not completed SkillMD's automated safety review yet. 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, and the skill stays under its author's original license.

Who published Pr Description?

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

Pr Description by bernardorubin — Agent Skill

Name: Pr Description
Author: bernardorubin

Pr Description

Use when the user asks to generate, write, draft, or update a pull request description on GitHub. Triggers on phrases like "write a PR description", "draft the PR body", "update the PR description", "fill in the PR", or "generate description for PR <number>". Operates on the current branch's PR by default, or one specified by number/URL. Updates the PR directly via `gh pr edit`, falls back to ~/Desktop/pr-description.md if the GitHub update fails.

bernardorubin Updated Sep 21, 2026

File contents

Generate PR Description

Generate a GitHub-ready PR description and update the PR directly on GitHub. Falls back to saving to Desktop if the GitHub update fails.

Arguments

Optional PR number or URL (e.g., 463 or https://github.com/org/repo/pull/463). If no PR is specified, auto-detect from the current branch.

Instructions

Step 1: Get PR Information

Try these in order until one works:

If a PR number/URL was provided: Run gh pr view <ARG> --json title,number,url,commits,files,baseRefName,headRefName
If no argument: Run gh pr view --json title,number,url,commits,files,baseRefName,headRefName (auto-detects current branch's PR)
If both fail: Fall back to git log and git diff --stat against the base branch (usually main or master)

Save the PR number and URL for later steps.

Step 2: Analyze Changes

From the PR data or git diff:

Review all commits to understand the scope of work
Analyze files changed to identify key areas
Group related changes into logical categories

Step 3: Generate PR Description

Create the description body (no H1 title — GitHub already shows the PR title). Use this structure:

## Summary - Bullet points summarizing what changed
## What's New - Tables for files changed, features added
## How to Test - Step-by-step instructions
## Test Plan - Checkbox items - [ ] for testing

Write the description to a temp file at /tmp/pr-description.md.

Step 4: Update PR on GitHub

Try to update the PR description directly on GitHub:

gh pr edit <PR_NUMBER> --body-file /tmp/pr-description.md

If successful: Tell the user the PR description was updated and show the PR URL.

If failed (e.g., no PR number, auth issues, not a GitHub repo): Fall back to saving at ~/Desktop/pr-description.md and tell the user it couldn't update GitHub directly, so the file was saved to Desktop instead.

Clean up the temp file after either outcome.

Format Requirements

Use ## for main sections, ### for subsections
Use tables for structured data (files, components, settings)
Use bullet points (-) for features/changes
Use numbered lists for step-by-step instructions
Use checkboxes (- [ ]) for test plan items
Include code blocks with proper language identifiers
Link related PRs if work spans multiple repos
Include file paths in backticks
Do NOT include any AI/Claude attribution or signatures
Do NOT wrap output in code fences - write raw markdown

---name: pr-descriptiondescription: Use when the user asks to generate, write, draft, or update a pull request description on GitHub. Triggers on phrases like "write a PR description", "draft the PR body", "update the PR description", "fill in the PR", or "generate description for PR <number>". Operates on the current branch's PR by default, or one specified by number/URL. Updates the PR directly via `gh pr edit`, falls back to ~/Desktop/pr-description.md if the GitHub update fails.---# Generate PR DescriptionGenerate a GitHub-ready PR description and update the PR directly on GitHub. Falls back to saving to Desktop if the GitHub update fails.## ArgumentsOptional PR number or URL (e.g., `463` or `https://github.com/org/repo/pull/463`). If no PR is specified, auto-detect from the current branch.## Instructions### Step 1: Get PR InformationTry these in order until one works:1. **If a PR number/URL was provided**: Run `gh pr view <ARG> --json title,number,url,commits,files,baseRefName,headRefName`2. **If no argument**: Run `gh pr view --json title,number,url,commits,files,baseRefName,headRefName` (auto-detects current branch's PR)3. **If both fail**: Fall back to `git log` and `git diff --stat` against the base branch (usually `main` or `master`)Save the PR number and URL for later steps.### Step 2: Analyze ChangesFrom the PR data or git diff:- Review all commits to understand the scope of work- Analyze files changed to identify key areas- Group related changes into logical categories### Step 3: Generate PR DescriptionCreate the description body (no H1 title — GitHub already shows the PR title). Use this structure:- `## Summary` - Bullet points summarizing what changed- `## What's New` - Tables for files changed, features added- `## How to Test` - Step-by-step instructions- `## Test Plan` - Checkbox items `- [ ]` for testingWrite the description to a temp file at `/tmp/pr-description.md`.### Step 4: Update PR on GitHubTry to update the PR description directly on GitHub:```bashgh pr edit <PR_NUMBER> --body-file /tmp/pr-description.md```**If successful**: Tell the user the PR description was updated and show the PR URL.**If failed** (e.g., no PR number, auth issues, not a GitHub repo): Fall back to saving at `~/Desktop/pr-description.md` and tell the user it couldn't update GitHub directly, so the file was saved to Desktop instead.Clean up the temp file after either outcome.## Format Requirements- Use `##` for main sections, `###` for subsections- Use tables for structured data (files, components, settings)- Use bullet points (-) for features/changes- Use numbered lists for step-by-step instructions- Use checkboxes (- [ ]) for test plan items- Include code blocks with proper language identifiers- Link related PRs if work spans multiple repos- Include file paths in backticks- Do NOT include any AI/Claude attribution or signatures- Do NOT wrap output in code fences - write raw markdown

Frequently asked questions