Create PR

Create PR

Generate GitHub pull request descriptions using the PR template at .github/PULL_REQUEST_TEMPLATE.md and referencing changes in the current branch. Outputs markdown and copies to clipboard.

When to Use

Activate this skill when the user:

• Uses /create-pr command with or without a repo name
• Says "create a PR description", "generate PR body", "make a pull request"
• Wants a PR description for their current branch

Important

This skill does NOT:

• ❌ Commit changes
• ❌ Push to remote
• ❌ Create the actual PR on GitHub

This skill ONLY:

• ✅ Generates PR title and description
• ✅ Outputs as markdown
• ✅ Copies to clipboard (platform-specific: pbcopy on macOS, xclip/xsel on Linux, clip.exe on Windows)

Workflow

Step 1: Identify Repository

If repo name is provided:

• Use the specified repository

If no repo name is provided:

• Check for .git in current workspace
• If multiple git repositories detected in workspace, ask user to specify which one

Validation:

• Verify the repository has a remote on GitHub
• Confirm current branch is not main, master, or the default branch

Step 2: Gather Branch Information

Run these commands in the repository directory:

# Get current branch name
git branch --show-current

# Get the base branch (usually main or master)
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'

# Get commit history since divergence from base
git log {base-branch}..HEAD --oneline

# Get full diff since divergence
git diff {base-branch}...HEAD

Step 3: Find and Read PR Template

Look for PR template in these locations (in order):

1. .github/PULL_REQUEST_TEMPLATE.md
2. .github/pull_request_template.md
3. docs/PULL_REQUEST_TEMPLATE.md
4. docs/pull_request_template.md
5. PULL_REQUEST_TEMPLATE.md
6. pull_request_template.md

CRITICAL: If template found:

• Read the template file using the Read tool
• Use the EXACT template structure - do not restructure or rename sections
• Preserve HTML comments (<!-- ... -->) - they provide context for reviewers
• Keep all checkbox items exactly as defined in the template
• Only fill in the content areas between section headers
• Do not add sections that don't exist in the template
• Do not remove sections - leave them empty or with "N/A" if not applicable

If no template found:

• Use a generic structure:

  ## Summary
  
  ## Changes
  
  ## Testing
  
  ## Related Issues

Step 4: Analyze Changes

Based on the git diff and commit history:

1. Categorize changes:

   • New features
   • Bug fixes
   • Refactoring
   • Documentation
   • Tests
   • Chores

2. Identify key files changed:

   • List the most significant file changes
   • Note any breaking changes or migrations

3. Extract commit messages:

   • Review commit messages for context
   • Identify patterns and themes

Step 5: Fill PR Template

Title Generation:

• Create concise title (50-70 characters max)
• Format: [Type] Brief description
• Types: feat, fix, refactor, docs, test, chore

Body Generation:

IMPORTANT: Follow the repository's template structure exactly.

1. Copy the entire template as the starting point
2. Keep all HTML comments - they guide reviewers and may be used by automation
3. Fill in content below each section header, after any HTML comments
4. For checkbox sections:
   • Mark applicable items with [x]
   • Leave others as [ ]
   • Do NOT remove any checkbox items
5. For text sections, fill based on:
   • Summary/Description: High-level overview of what changed and why
   • Changes: Bulleted list of key changes from the diff
   • Testing: How to test/verify the changes (use numbered steps)
   • Related Issues: Extract from commit messages or branch names. Use short IDs (e.g., "Fixes WOOSHIP-456") NOT full URLs
   • Screenshots: Add if UI changes, otherwise write "N/A" or "N/A - Logic fix, no visual changes"

Step 6: Generate Final Output

Format the complete PR content:

## Title

{Generated PR title}

## Description

{Filled PR template body}