github-pr-creationlisted

# GitHub PR Creation Creates Pull Requests with task validation, test execution, and Conventional Commits formatting. ## Quick Start ```bash # 1. Verify GitHub CLI gh --version && gh auth status # 2. Gather information git log develop..HEAD --oneline git diff develop --stat git rev-parse --abbrev-ref HEAD # 3. Run project tests make test # or: pytest, npm test # 4. Create PR gh pr create --title "..." --body "..." --base develop --label feature ``` ## Core Workflow ### 1. Verify Environment ```bash gh --version && gh auth status ``` If not installed: `brew install gh` then `gh auth login` ### 2. Confirm Target Branch **Always ask user**: ``` 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 ```bash # Current branch git rev-parse --abbrev-ref HEAD # Commits since base branch git log [base-branch]..HEAD --oneline # Files changed git diff [base-branch] --stat # Remote tracking status git status -sb ``` ### 4. Search for Task Documentation Look for task files in these locations: 1. `.kiro/specs/*/tasks.md` 2. `docs/specs/*/tasks.md` 3. `specs/*/tasks.md` 4. Any `tasks.md` in project root ### 5. Analyze Commits For each commit, identify: - **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` patte