Agent skill

pr-description-writer

Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the PR via the gh CLI.

Varnan-Techgithub.com/Varnan-TechGitHub ↗
claude-codecopilotMIT
Install
npx skills add Varnan-Tech/opendirectory --skill pr-description-writer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.0.0
Declared author: OpenDirectory
Requires: [claude-code, gemini-cli, github-copilot]
Path: skills/pr-description-writer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 571
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PR Description Writer Read the current branch diff and write a complete GitHub pull request description. Create or update the PR with one command. ## Writing Style Apply to all generated PR descriptions: - Active voice. "Adds X" not "X has been added." - Present tense for summary ("Adds caching layer"), past tense for context ("The old approach caused N requests per render") - Short sentences, one idea per bullet - No em dashes — use a comma or period instead - No filler: "this PR", "this commit", "as per the discussion" - Specifics beat generalities: "reduces p95 latency from 800ms to 90ms" beats "improves performance" --- ## Step 1: Check Setup Confirm `gh` is authenticated: ```bash gh auth status ``` If not authenticated: `gh auth login` and follow the prompts. Confirm the current directory is a git repo with an active branch: ```bash git branch --show-current ``` If detached HEAD or no branch, stop and ask the user which branch they want to describe. --- ## Step 2: Gather Diff Context Run all three commands to build context: **File summary (what changed):** ```bash git diff main...HEAD --stat ``` **Commit messages (why it changed):** ```bash git log main...HEAD --oneline ```

What's inside
Steps it walks through
  1. Writing Style
  2. Step 1: Check Setup
  3. Step 2: Gather Diff Context
  4. Step 3: Read the Format Guide
  5. Step 4: Generate the Description
  6. Step 5: Create or Update the PR
Ships with 3 files
  • README.md
  • evals/evals.json
  • references/pr-format-guide.md
Commands it runs
gh auth status
git branch --show-current
git diff main...HEAD --stat
git log main...HEAD --oneline
if git rev-parse origin/main &>/dev/null 2>&1; then
elif git rev-parse main &>/dev/null 2>&1; then
else
fi
git diff $BASE...HEAD
gh pr view --json title,body,baseRefName 2>/dev/null
More from opendirectory
All skills →
About this skill
What does the pr-description-writer skill do?

Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the PR via the gh CLI.

How do I install it?

Run `npx skills add Varnan-Tech/opendirectory --skill pr-description-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going