create-pr

# Create PR Complete workflow for creating pull requests following project standards. When explicitly invoked with extra text, treat that text as additional context for branch naming, commit context, and PR title and body generation. Compress it into a short plain-language branch name rather than copying the full text. ## Process 1. **Preferred execution** - If subagents are available, use `github-dev:pr-creator` for the full workflow. - Pass along any extra invocation text plus session findings and motivation as additional context. - Otherwise follow the manual steps below. 2. **Verify staged changes** exist with `git diff --cached --name-only` 3. **Branch setup** - If on main/master, create a short branch first: `feature/short-topic`, `fix/short-topic`, or `docs/short-topic` - Keep the branch suffix to 2-4 short words - Avoid long, overly specific, or sentence-like branch names - Use `github-dev:commit-creator` subagent to handle staged changes if needed, and pass session findings and motivation into the commit context 4. **Documentation check** - Update README.md or docs based on changes compared to target branch - For config/API changes, use `mcp__tavily__tavily_search` to verify info and include sources 5. **Analyze all commits** - Use `git diff <base-branch>...HEAD` to review complete changeset - PR message must describe all commits, not just latest - Focus on what changed from reviewer perspective 6. **Create PR** - Use `...