Create a pull request from the current branch. Triggers on create PR/open PR/make PR/submit PR/push PR/raise PR/open a pull request/create a pull request/ready to merge/branch is ready when the user wants to turn their current branch into a GitHub pull request with a well-structured description
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Create a pull request from the current branch with a well-structured description derived from commits and diffs.
Before doing anything, check for repo-specific instructions that override the defaults below:
# Check for conventions in order of priority
cat CLAUDE.md 2>/dev/null || cat AGENTS.md 2>/dev/null || cat .github/CONTRIBUTING.md 2>/dev/null
Look for:
main)git branch --show-current
git status
git log main..HEAD --oneline
main directly, stop and ask the user to create a feature branch firstfeat/, fix/, chore/, ci/, docs/, test/, refactor/no-jira/ or no-ticket/ when there is no associated issuegit push origin <branch_name>
Always use the explicit branch name (not HEAD).
Use Conventional Commits format — NO scopes in parentheses. CI rejects
feat(scope):, only feat: is valid.
<type>: <description>
Types: feat, fix, docs, chore, refactor, test, perf, ci
Read it and replace all placeholder text with content derived from commits and diffs:
cat .github/pull_request_template.md
Fill in every section. Leave any screenshots/video section for the author to populate.
Use this structure:
## Background
- {Why this change is needed}
## What Has Changed
- {What this PR introduces or modifies}
## Screenshots/Video
- {Leave for author}
## Checklist
- [ ] Self-review completed
- [ ] Tests added or updated
- [ ] Tested locally
## Reference Issue
- Closes #{issue-number} ← only include if there is an associated issue
gh pr create \
--title "<title>" \
--body "<description>" \
After creating the PR, do not perform any additional commits.
Share the URL so the user can review it immediately.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.
The English summary is being prepared. Showing the original description.
Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.
The English summary is being prepared. Showing the original description.
Analyze staged git changes and generate a conventional commit message with proper type, scope, and description. Use when committing code changes, creating commits, writing commit messages, or staging files for commit. Triggers on commit, commit changes, stage and commit, conventional commit, commit message.
The English summary is being prepared. Showing the original description.
Detects deeply nested loops with duplicated inline logic and recommends extracting into small, named functions. Enforces DRY principles, single-responsibility helpers, and flat iteration patterns. Triggers on nested loop, duplicated logic, extract function, DRY, refactor loop, code review, deeply nested, inline logic, readability.
The English summary is being prepared. Showing the original description.
Analyze the current repo structure, build system, test setup, and conventions to provide a practical onboarding guide. Use when new to a codebase, joining a project, or wanting to understand how a repo is organized. Triggers on getting started, new to repo, onboard, how does this repo work, repo structure, codebase overview.
The English summary is being prepared. Showing the original description.
End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.
The English summary is being prepared. Showing the original description.