GitHub PR Creation

Quick Start

# 1. Verify GitHub CLI
gh --version && gh auth status

# 2. Gather information (Claude does this directly)
git log develop..HEAD --oneline        # Commits to include
git diff develop --stat                 # Files changed
git rev-parse --abbrev-ref HEAD        # Current branch

# 3. Run project tests
make test  # or: pytest, npm test

# 4. Create PR (after generating content)
gh pr create --title "..." --body "..." --base develop --label feature

Core Workflow

1. Verify Environment

gh --version && gh auth status

brew install gh

gh auth login

2. Confirm Target Branch

I'm about to create a PR from [current-branch] to [target-branch]. Is this correct?
- feature branch → develop (90% of cases)
- develop → master/main (releases)

3. Gather Information

# Current branch
git rev-parse --abbrev-ref HEAD

# Commits since base branch
git log [base-branch]..HEAD --pretty=format:"%H|%an|%ai|%s"

# Commits with full details (for context)
git log [base-branch]..HEAD --oneline

# Files changed
git diff [base-branch] --stat

# Remote tracking status
git status -sb

4. Search for Task Documentation

1. .kiro/specs/*/tasks.md

2. docs/specs/*/tasks.md

3. specs/*/tasks.md

4. Any

   tasks.md

   in project root

• Task IDs (format:

  Task X

  or

  Task X.Y

  )
• Task titles and descriptions
• Requirements (format:

  Requirements: X, Y, Z

  )

5. Analyze Commits

• Type: feat, fix, refactor, docs, test, chore, ci, perf, style
• Scope: component/module affected (kebab-case)
• Task references: look for

  task X.Y

  ,

  Task X

  ,

  #X.Y

  patterns
• Breaking changes: exclamation mark after type/scope, or

  BREAKING CHANGE

  in body

6. Verify Task Completion

1. Identify main task from branch name (e.g.,

   feature/task-2-*

   → Task 2)
2. Find all sub-tasks (e.g., Task 2.1, 2.2, 2.3)
3. Check which sub-tasks are referenced in commits
4. Report missing sub-tasks

✗ Task 2 INCOMPLETE: 1/3 sub-tasks missing
- Task 2.1: ✓ Implemented
- Task 2.2: ✓ Implemented
- Task 2.3: ✗ MISSING

7. Run Tests

• If Makefile with

  test

  target:

  make test

• If package.json:

  npm test

• If Python project:

  pytest

8. Determine PR Type

feat(scope):

fix(scope):

hotfix(scope):

release:

refactor(scope):

9. Generate PR Content

references/pr_templates.md

<type>(<scope>): <description>

• Type: dominant commit type (feat > fix > refactor)
• Scope: most common scope from commits, or task-related scope (kebab-case)
• Description: imperative, lowercase, no period, max 50 chars

10. Suggest Labels

gh label list

11. Create PR

gh pr create --title "[title]" --body "$(cat <<'EOF'
[body content]
EOF
)" --base [base_branch] --label [labels]

Information Gathering Checklist

• Current branch name
• Base branch confirmed with user
• List of commits with types and scopes
• Files changed summary
• Task documentation (if exists)
• Task completion status
• Test results (must pass)
• Available labels in repo

Error Handling

brew install gh && gh auth login

Important Rules

• NEVER modify repository files (read-only analysis)
• ALWAYS confirm target branch with user
• ALWAYS run tests before creating PR
• ALWAYS show PR content for approval before creating
• NEVER create PR without user confirmation
• ALWAYS use HEREDOC for body to preserve formatting

Related Skills

• git-commit - Commit message format and conventions

References

• references/pr_templates.md

  - Complete PR templates for all types

• references/conventional_commits.md

  - Commit format guide