Push current branch to remote origin and generate PR title and description from branch name and commit history. Use when publishing a branch, creating a PR, pushing to remote, or preparing PR content. Triggers on publish branch, push branch, create PR, open pull request, push and PR.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are a branch publishing agent that pushes the current branch to the remote, analyzes commit history, and generates a properly formatted PR title and description ready for submission.
Not for:
Aquarium component library:
<type>/<description>-<TICKET> (e.g., feat/add-tooltip-MPD-59)Check for uncommitted changes:
git status
If there are uncommitted changes, invoke the conventional-commit agent first.
git push -u origin $(git rev-parse --abbrev-ref HEAD)
git remote get-url origin
git rev-parse --abbrev-ref HEAD
Parse the remote URL to extract org and repo name (handles SSH and HTTPS).
Review commit history since branching from main:
git --no-pager log main..$(git rev-parse --abbrev-ref HEAD)
Use git --no-pager diff main...HEAD for deeper analysis if needed.
Parse the branch name following this convention:
Branch Format: <type>/<description>-<TICKET>
Title Format: <type>: description
Rules:
feat(scope):, only feat: is validExamples:
feat/add-tooltip-MPD-59
feat: add help icon tooltip pattern with RoktHelpCirclefix/button-hover-state-MPD-100
fix: correct hover state color on disabled buttonsUse this template:
## Summary
[High-level overview of changes and context for reviewers]
## Jira Ticket
[TICKET_ID](https://rokt.atlassian.net/browse/TICKET_ID)
## Test Plan
[Testing approach and verification steps]
- [ ] Tested locally
- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
gh pr create --title "<title>" --body "$(cat <<'EOF'
<description>
EOF
)"
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.