pr-description-writerlisted

# 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: ```bash # Check if current branch has a PR (returns 0 if PR exists, non-zero otherwise) gh pr view --json number,title,body,url 2>/dev/null # If you just need to know if a PR exis