| name | pr |
| description | Create a pull request by analyzing code changes and commit history. |
Process
- Run
git fetch --all --pruneto ensure the latest changes are fetched - Check git status and current branch
- Get commit history from [origin] to HEAD
- Analyze
git diff [origin]...HEADto understand changes - Prompt the user for the [origin] (don't make assumptions)
- Create a pull request with a descriptive title and body based on actual code changes (
gh) - Assign the current git user to the created PR
Analysis
- Examine modified files and functionality changes
- Understand technical implementation and business impact
- Focus on what changed, not just commit messages
Rules
- PR title MUST use Conventional Commits format:
type(scope): description- Lowercase, imperative mood (same as commit messages)
- Optional Notion ticket ID in brackets at end:
[TL-1234]
- Write meaningful descriptions based on diff analysis
- Never include checkboxes, test plans, or checklists
- Avoid ANSI codes in descriptions
- Pass markdown directly to gh, never use heredoc
- Use markdown and differentiate between sections using ###
- When writing PR titles or bodies, wrap every code identifier (variable names, params, functions, keys, enum values) in backticks.