create-prlisted

# Creating a Pull Request ## Workflow ### Step 1: Verify branch state ```bash CURRENT=$(git branch --show-current) DEFAULT=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name') ``` - If `$CURRENT` equals `$DEFAULT` or is `develop`/`release/*`/`hotfix/*`: inform user they are on a protected branch, cannot create PR from here - If uncommitted changes exist: commit first (use git-commit skill) - If branch not pushed: `git push -u origin $CURRENT` ### Step 2: Analyze changes ```bash DEFAULT=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name') git log --format="%s%n%b" "$DEFAULT..HEAD" git diff --name-only "$DEFAULT..HEAD" git diff --stat "$DEFAULT..HEAD" ``` From the diff and commits, identify: - **Type**: primary change type (feat, fix, refactor, chore, perf) - **Intent**: business/technical goal (1-2 sentences) - **Entry point**: most critical changed file for reviewer - **Sensitive areas**: files needing extra scrutiny (auth, payments, data) - **Breaking changes**: `!` in commits or BREAKING CHANGE footer - **Migrations**: database or schema changes ### Step 3: Generate title Conventional Commits format: `<type>[scope]: <description>` - Imperative mood, under 72 chars, no period, English only - Match the project's commit style (check `git log --format="%s" -20`) NEVER add task ID, issue number, or other metadata to the title: **❌ Wrong:** ``` feat(messages): add server-only synthetic mailbox archive parser (BP-1234) ``` **✅ Correc