Agent skill · writing content · aiskillstore
pr-description-writer
Generates comprehensive, reviewer-friendly PR descriptions with visual diagrams, summary tables, collapsible sections, and structured test plans. Optimized for readability without sacrificing detail.
Why this skill is useful
Adds structured templates and scripts for generating detailed PR descriptions that enhance clarity and organization for reviewers.
What it needs
Requires bash installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
PR Description Writer Skill When to Use This Skill Use this Skill when: Creating or updating a PR description for a feature branch. The PR has multiple related changes that need clear organization. You want a description that helps reviewers understand the "why" and "what" quickly while having access to detailed context. You're preparing a PR for review and want it to be self-documenting. This Skill is designed to work with any repository but is especially tuned for Django/Python backends, React frontends, and infrastructure changes. Example Prompts "Use pr-description-writer to create a PR description for my current branch." "Generate a comprehensive PR description for PR #1234 using the pr-description-writer Skill." "Update the PR description for my feature branch to match our standard format." --- Workflow: Gathering Context Before writing the PR description, always gather the complete picture of all changes that will be included in the PR. This means: 1. Local uncommitted changes (staged + unstaged) 2. Local commits not yet pushed 3. Commits already pushed to the remote branch 4. Existing PR details (if a PR already exists) Step 1: Detect If Current Branch Has a PR Use gh pr view to check if the current branch already has an associated PR: Interpretation: Exit code 0 + JSON output → PR exists, use the PR number for updates Exit code non-zero → No PR yet, description will be for a new PR Step 2: Identify the Base Branch Determine what branch the PR targets (or will target). Use this detection order: Detection Priority: 1. Existing PR base – If PR exists, always use its base branch 2. GitHub default – gh repo view --json defaultBranchRef is authoritative 3. Git remote HEAD – Works offline, reflects GitHub's default 4. Common branch names – Check for main/master/release/develop Smart Detection Script: Step 3: Gather ALL Changes CRITICAL: The PR description must account for ALL changes, not just the latest commit. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/pr-description-writer