github-pr-creationlisted

# GitHub PR creation Creates Pull Requests with task validation, test execution, and Conventional Commits formatting. ## Current state !`git rev-parse --abbrev-ref HEAD 2>/dev/null` !`git log @{u}..HEAD --oneline 2>/dev/null || echo "(no upstream tracking)"` ## Core workflow ### 1. Confirm target branch **ALWAYS ask user before proceeding:** ``` Creating PR from [current-branch] to [target-branch]. Correct? ``` | Branch flow | Typical target | |-------------|---------------| | feature/* | develop | | fix/* | develop | | hotfix/* | main/master | | develop | main/master | ### 2. Search for task documentation Look for task/spec files that describe what this PR should accomplish. Common locations by tool: | Tool/Convention | Path | |-----------------|------| | Spec2Ship (s2s) | `.s2s/plans/*.md` (look for active plan matching branch name or commits) | | AWS Kiro | `.kiro/specs/*/tasks.md` | | Cursor | `.cursor/rules/*.md`, `.cursorrules` | | Trae | `.trae/rules/*.md` | | GitHub Issues | `gh issue list --assignee @me --state open` | | Generic | `docs/specs/`, `specs/`, `tasks.md`, `TODO.md` | Extract task IDs, titles, descriptions, and requirements references when found. ### 3. Analyze commits For each commit on this branch, identify type, scope, task references, and breaking changes. Map commits to documented tasks when task files exist. ### 4. Verify task completion If task documentation exists: 1. Identify main task from branch name (e.g., `feature/task-2-*` ->