Skip to content
Skills Library
Programming · Writing

pr-description

/pr-description

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.

Licence
AGPL-3.0
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

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.

Original author description

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.

How it works

  1. When to Use
  2. Goals
  3. Workflow
  4. Commands
  5. Body Structure
  6. Quality Bar
  7. Optional Enhancements
Original SKILL.md headings · 71 lines, 266 words
SKILL.md preview
---
name: pr-description
description: 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.
Files in this package (2)
  • SKILL.md 2 KB
  • references/pr-body-template.md 1 KB

Versions

RepositoryScoreLicence
This page · basicmachines-co/basic-memory100AGPL-3.0
tanstack/ai100MIT
dxos/dxos100Apache-2.0
sanity-io/sanity100MIT
gosodax/sodax-sdks100MIT
Epsilon0xCell/pr-shepherd-skills100MIT
jdx/mise100MIT
Kuan-AI-com/agent-skills100MIT
The01Geek/prflow100MIT

Database snapshot: 13.11.2026 · package version 6740a134bf81 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100v1-pr-description
    Use when writing or updating a GitHub PR title or description. Triggers on "write PR description", "update PR body", or "PR title".
  • 90visual-pr
    Write or update a pull request's description, with diagrams of what changed. Use whenever opening a PR or writing or refreshing a PR description in a repo, or when the user invokes visual-pr by name.
  • 100github-pr-description
    Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR…
  • 92pr
    Use when writing a PR body.
  • 92pr
    Use when writing a PR body.
  • 100pr-writing
    Write a PR description. Use when writing or updating a PR title or description, or opening a new PR.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.