create-pr

Create Pull Request Content

Generate all content needed for a pull request: commit message, PR title, and PR body.

Step 1: Gather Information

YOU MUST EXECUTE THESE COMMANDS IN ORDER. DO NOT SKIP ANY STEP.

Step 1.1: Get branch info:

git rev-parse --abbrev-ref HEAD

Step 1.2: Get file change summary (THIS IS CRITICAL - you must see ALL files):

DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "master") && echo "=== COMMITTED AHEAD OF BASE ===" && git diff ${DEFAULT_BRANCH}...HEAD --stat -- ':!docs/soup.md' ':!.soup.json' && echo "=== STAGED ===" && git diff --cached --stat -- ':!docs/soup.md' ':!.soup.json' && echo "=== UNSTAGED ===" && git diff --stat -- ':!docs/soup.md' ':!.soup.json'

Step 1.3: Get the full diff (committed + staged + unstaged changes):

DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "master") && echo "=== COMMITTED AHEAD OF BASE ===" && git diff ${DEFAULT_BRANCH}...HEAD -- ':!docs/soup.md' ':!.soup.json' && echo "=== STAGED ===" && git diff --cached -- ':!docs/soup.md' ':!.soup.json' && echo "=== UNSTAGED ===" && git diff -- ':!docs/soup.md' ':!.soup.json'

NOTE: Include ALL three sections (committed, staged, unstaged) in your analysis. Changes may appear in any combination depending on the workflow.

Step 1.4: Find the PR template:

cat .github/pull_request_template.md 2>/dev/null || cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || echo "No PR template found"

Step 1.5: Check for JIRA ticket:

echo $JIRA_TICKET

CRITICAL: The PR summary MUST mention ALL files shown in the Step 1.2 --stat output. Count the files and verify your summary accounts for all of them.

Step 2: Generate Output

Output ONLY the following format. Start immediately with "COMMIT MESSAGE:" - no preamble or commentary:

COMMIT MESSAGE:
<one line, max 80 characters>
---
PR TITLE:
<one line, max 80 characters>
---
PR BODY:
<filled PR template - can contain any valid markdown>

IMPORTANT formatting rules:

• Section labels must be plain text exactly as shown: "COMMIT MESSAGE:", "PR TITLE:", "PR BODY:"
• Do NOT use markdown formatting on the labels (no bold, no code blocks around them)
• Separate sections with exactly "---" on its own line
• The PR BODY content can contain any valid markdown (code blocks, lists, etc.)

Commit Message Guidelines

• One line only, maximum 80 characters
• Start with a verb (Add, Fix, Update, Remove, Refactor, etc.)
• Be specific but concise
• No period at the end
• NO footers, NO co-authors, NO signatures

PR Title Guidelines

• One line only, maximum 80 characters
• Should summarize the overall purpose of the PR
• Can be similar to commit message but may be slightly more descriptive

PR Body Guidelines

Summary

IMPORTANT: The Summary section heading must be ## Summary (h2), not # Summary (h1).

Structure the summary as follows:

1. Start with a short paragraph describing the big picture of the changes
2. Follow with Key changes: (bold)
3. Add a bullet list of all changes made, one per line. Similar changes can be summarized together.

Types of changes

CRITICAL: Preserve ALL checkbox items from the template exactly as they appear. Mark applicable items with [x] and leave non-applicable items as [ ]. Never delete, modify, or omit any checkbox items from the original template.

Checklist

CRITICAL: Preserve ALL checkbox items from the template exactly as they appear. Mark applicable items with [x] and leave non-applicable items as [ ]. Never delete, modify, or omit any checkbox items from the original template.

Jira Tickets

If the PR template does NOT contain a Jira Tickets section:

• Do not add one

If the PR template contains a Jira Tickets section:

• If JIRA_TICKET env var is set: replace any placeholder (e.g., XXX-XXXX) with the value from the environment variable
• If JIRA_TICKET env var is NOT set or empty: omit the entire Jira Tickets section from the output

Further comments (if required)

This section should ONLY be filled if one of the following applies:

• Breaking changes are introduced
• Complex database migration is required
• Reprocessing of existing data is required

If NONE of the above apply, omit this entire section from the output.

If the section is required, write a paragraph explaining the breaking changes, complex database migration, or reprocessing of existing data with any useful information for the reviewer to understand why it is needed and what actions to take.

Note: When this section is filled due to database migration or reprocessing of existing data, the corresponding checklist item about database changes requiring migration/downtime/reprocessing should also be marked with [x].

Important Rules

• NEVER add "Generated with Claude Code" or similar signatures to commit messages or PR body
• NO emojis unless explicitly requested
• Before generating PR content, ensure the run-linters skill has been executed to verify code quality