New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR Description Writer

by Varnan-Tech in Varnan-Tech/opendirectory

A skill your agent uses when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch.

MITAuto-check passedDevelopment

Install PR Description Writer

skills CLI
$ npx skills add Varnan-Tech/opendirectory --skill pr-description-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Varnan-Tech/opendirectory pr-description-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-description-writer .claude/skills/pr-description-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-description-writer
GitHub stars
674
Token cost
~1k tokens
SKILL.md length
495 words
Files
4 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch.

  • Works in 5 steps: Check Setup → Gather Diff Context → Read the Format Guide → …
  • The user asks to write
  • SKILL.md covers Writing Style, Step 1: Check Setup, Step 2: Gather Diff Context and Step 3: Read the Format Guide, plus 2 more sections
  • Calls gh and git

What it does

PR Description Writer is an agent skill from Varnan-Tech/opendirectory. 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.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/pr-format-guide.md`). Compatibility notes: ["claude-code","gemini-cli","github-copilot"]

It sits in Development, covering Pull requests and Commit messages. It works with GitHub. The repository describes itself as: AI Agent Skills built for Founders who hate Marketing. The licence is MIT.

When your agent uses it

  • The user asks to write
  • Update a GitHub pull request description for the current branch

Example prompts

  • “/pr-description-writer”

Requirements

  • Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"]

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Check Setup
  2. Gather Diff Context
  3. Read the Format Guide
  4. Generate the Description
  5. Create or Update the PR

What it can do on your machine

Read from SKILL.md and the folder at commit 62e437a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    ["claude-code","gemini-cli","github-copilot"]

    From compatibility in the SKILL.md frontmatter.

Context cost

PR Description Writer loads about 1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 495 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Varnan-Tech/opendirectory at commit 62e437a, republished under its MIT licence (© Varnan-Tech). 495 words, ~1,033 tokens.

Download SKILL.mdSave it as .claude/skills/pr-description-writer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
pr-description-writer
description
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.
compatibility
["claude-code","gemini-cli","github-copilot"]
author
OpenDirectory
version
1.0.0

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

Full diff (how it changed):

Use origin/main first (always up to date), fall back to local main, then master:

bash
if git rev-parse origin/main &>/dev/null 2>&1; then
  BASE=origin/main
elif git rev-parse main &>/dev/null 2>&1; then
  BASE=main
else
  BASE=master
fi
git diff $BASE...HEAD

If the diff is very large (over 500 lines), read the --stat summary and the commit messages only. Also read the first 200 lines of the diff to understand the primary changes without processing the entire output.

Also check for an existing PR and read its current title/body:

bash
gh pr view --json title,body,baseRefName 2>/dev/null

Step 3: Read the Format Guide

Read references/pr-format-guide.md in full before writing anything. Internalize:

  • Required sections and their order
  • How to write each section
  • What to include vs omit
  • The testing section format
Show full SKILL.md (229 more words)Show less

Step 4: Generate the Description

Write the PR description using the format from references/pr-format-guide.md.

Rules:

  • Every bullet in the Changes section must trace to something in the diff
  • Do not invent testing steps that are not implied by the code changes
  • If a section has no relevant content, omit it entirely (do not write "N/A" or leave it empty)
  • Screenshots section: only include if there are UI changes visible in the diff
  • If commit messages explain the "why", use that context in the Summary

QA checkpoint: Before presenting, verify:

  • Summary is 1-2 sentences, active voice, no filler
  • Every change bullet is specific and traces to the diff
  • No invented metrics or outcomes
  • Testing steps are actionable (someone could follow them)
  • No em dashes in any line

Step 5: Create or Update the PR

Present the description to the user and ask: "Ready to create the PR, update the existing one, or output only?"

Create a new PR:

Pass the body via stdin to handle backticks, quotes, and newlines safely:

bash
gh pr create --title "TITLE_HERE" --body-file - << 'EOF'
BODY_HERE
EOF

Suggest a title based on the commit messages and diff summary. The title should be imperative mood, under 72 characters: "Add Redis caching for user session lookups" not "Added caching".

Update an existing PR:

bash
gh pr edit --body-file - << 'EOF'
BODY_HERE
EOF

Output only: Present the title and body in a code block for manual copy-paste.

After creating or updating, confirm: "PR description updated. View it at: [URL]"

© Varnan-Tech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/pr-description-writer of Varnan-Tech/opendirectory.

  • SKILL.md
  • README.md
  • evals/evals.json
  • references/pr-format-guide.md

Open the folder on GitHubat commit 62e437a

Compare with similar skills

PR Description Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Description Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Description Writer this skillVarnan-Tech/opendirectory674—~1kAutomated safety check: PassMIT
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Gh PR Metadatamodule-federation/core2.7k—~1kAutomated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Gh PR Metadata

    module-federation/core

    Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.

    2.7k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Submit PR

    tisfeng/Easydict

    创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。

    15k GitHub stars~595 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from Varnan-Tech/opendirectory

All 61 skills in this repo

  • Graphic Ebook

    Varnan-Tech/opendirectory

    Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

    674 GitHub stars~5k tokensUpdated 1 mo ago
    Auto-check passed

  • Docs From Code

    Varnan-Tech/opendirectory

    Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture.

    674 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Graphic Chart

    Varnan-Tech/opendirectory

    Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6.

    674 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Graphic Gif

    Varnan-Tech/opendirectory

    Creates animated looping GIFs from CSS animations (default) or AI image-to-video.

    674 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

  • Map Your Market

    Varnan-Tech/opendirectory

    Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences…

    674 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Newsletter Digest

    Varnan-Tech/opendirectory

    Aggregates RSS feeds from the past week, synthesizes the top stories using Gemini, and publishes a newsletter digest to Ghost CMS.

    674 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about PR Description Writer

What does PR Description Writer do?

A skill your agent uses when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. PR Description Writer is an agent skill from Varnan-Tech/opendirectory. Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch.

When should I use PR Description Writer?

PR Description Writer fits situations like: the user asks to write; update a GitHub pull request description for the current branch.

How do I install PR Description Writer in Claude Code?

Run `npx skills add Varnan-Tech/opendirectory --skill pr-description-writer -a claude-code`. Or copy the skill folder (skills/pr-description-writer in Varnan-Tech/opendirectory) into .claude/skills/pr-description-writer in your project. Claude Code loads it when a task matches its description.

How do I install PR Description Writer in Codex?

Run `npx skills add Varnan-Tech/opendirectory --skill pr-description-writer -a codex`. Or copy the skill folder (skills/pr-description-writer in Varnan-Tech/opendirectory) into .agents/skills/pr-description-writer in your project. Codex loads it when a task matches its description.

Can I use PR Description Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Varnan-Tech/opendirectory --skill pr-description-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-description-writer, .gemini/skills/pr-description-writer, .github/skills/pr-description-writer and .opencode/skills/pr-description-writer in your project.

What does PR Description Writer need to run?

Going by SKILL.md and its folder, PR Description Writer needs the command-line tools its instructions call (gh and git). Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"].

Does PR Description Writer access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR Description Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Description Writer use?

PR Description Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Description Writer use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 975 tokens, read only when the agent opens those files.

What are the alternatives to PR Description Writer?

Skills that share tags, products or a category with PR Description Writer: PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Gh PR Metadata (module-federation/core, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Description Writer?

Varnan-Tech (a GitHub organization) maintains it in Varnan-Tech/opendirectory, which has 674 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on August 16, 2026.

Source: Varnan-Tech/opendirectory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.