| name | git-pr |
| description | Analyzes changes in the current branch, creates a PR with title and body, then submits it to GitHub. Use when you need to create a pull request. |
| allowed-tools | Bash(gh *), Bash(git diff *), Bash(git status *), Bash(git log *), Bash(git show *), Bash(git push *) |
Analyze the changes in the current branch, generate a PR title and body in English, and create a GitHub pull request.
1. Determine the base branch dynamically:
- Check if `origin/develop` exists using `git show-ref --verify refs/remotes/origin/develop`
- If it exists, use `develop` as ``
- Otherwise, fall back to `gh repo view --json defaultBranchRef -q .defaultBranchRef.name` (fallback to `main` if unavailable)
2. Check current branch status and commit history
3. Get the diff using `git diff ...HEAD` to see all commits since branching from the base
4. Analyze the changes and generate PR title and body
5. Push the branch to remote if needed with `-u` flag
6. Create the PR using `gh pr create --base `
- Write both PR title and body in English
- PR title: under 70 characters, concise and descriptive
- PR body structure:
- Summary section with 2-3 bullet points of major changes only
- Focus on overall architecture changes and data flow, not individual file changes
- Use mermaid diagrams when helpful for visualization
- Keep it concise - ignore minor changes
