Create Draft Pr

Find PR Template

• Search tracked files: git ls-files | grep -i pull_request_template
• If multiple results found (e.g., PULL_REQUEST_TEMPLATE/ directory with multiple files), list them and ask user which to use
• If single file found, read it
• If none found, use minimal structure: Summary only

Fill Template

• Analyze diff and commit history
• Cross-reference with plan document if available
• If template found: fill each section present in the template based on actual changes
• If no template: write a Summary of what changed and why
• If the branch name contains a recognizable issue/ticket ID, include it (e.g., Fixes #123, Fixes FOO-123). If none found, skip
• PR title: Search .github/ for title validation rules (e.g., pr-title-checker-config.json, workflows with title checks, commitlint/semantic-release configs). If found, generate a title matching the required pattern. If none found, generate a concise title (under 70 chars)

Fetch Available Labels

• gh label list --limit 200
• Recommend 1-3 high-signal labels with short reasons

Confirm and Create

• Display: base branch, title, body, label recommendations
• Ask: "Create draft PR with these details?"
• If approved:
  1. Write body to temp file to avoid shell escaping issues
  2. gh pr create --draft --base <base> --title "<title>" --body-file <temp file>
  3. Add labels: gh pr edit <number> --add-label <labels>
  4. Clean up temp file
  5. Display PR URL
• If not approved, provide copy-paste output only