Avi Pr Flow
npx machina-cli add skill avi1234/claude-team-plugins/avi-pr-flow --openclawYou are helping me with a complete PR workflow. Follow these steps:
1. Check Branch Safety
- Get current branch
- If "main" or "master", STOP with error
2. Review Code
- Run
/pr-review-toolkit:review-pr - Fix any suggestions before committing
3. Commit and Push
- Stage all changes
- Generate meaningful commit message from staged diff
- Commit and push to remote
4. Create or Find PR
- Check if PR exists for current branch
- If no PR:
- Extract ticket from branch name (e.g., ME-12345)
- Use $ARGUMENTS as title if provided, otherwise generate:
<ticket>: <summary> - Generate PR body with summary and key modifications
- Create PR and extract PR number
5. Request Bugbot Review
- Comment "bugbot review"
- Poll for bugbot/cursor response (60s intervals, max 5 attempts)
- If timeout, report to me
6. Handle Bugbot Feedback
- Fetch and display all review comments
- If no issues → skip to CircleCI check
- If issues found:
- Ask me to fix and wait for confirmation
- After confirmation: commit, push
- Reply "Fixed! ✅" to all comment IDs
- Request bugbot review again (poll 60s, max 5 attempts)
7. Check CircleCI
- Check pipeline status using CircleCI MCP (current repo + branch)
- If running: poll 60s, max 15 attempts (display "waiting...")
- If failed: show logs, ask for fixes, commit/push after confirmation, re-check
- If success: report "CI passed ✅"
8. Show Final Status
- Display PR state and reviews
Notes
- Stop on any command failure and report error
- Keep me informed at each step
Source
git clone https://github.com/avi1234/claude-team-plugins/blob/main/team1-plugin/skills/avi-pr-flow/SKILL.mdView on GitHub Overview
Avi Pr Flow automates the end-to-end PR lifecycle from committing changes to final CI checks. It enforces branch safety, runs a code review, creates or finds a PR based on your branch, coordinates a bugbot review, and tracks CircleCI status to present a final PR state.
How This Skill Works
The workflow uses Bash git and gh tools to inspect the current branch, aborting if it is main or master. It invokes the code review step via /pr-review-toolkit:review-pr, generates a meaningful commit message from the staged diff, and pushes to the remote. It then creates or locates a PR using a ticket extracted from the branch name (e.g., ME-12345) or a provided ARGUMENTS title, builds a PR body with a summary and key changes, and proceeds to request a bugbot review, poll for feedback, and monitor CircleCI for the final status.
When to Use It
- When you want an end-to-end PR automation from commit to review and CI status.
- When you must prevent PRs from main/master and enforce branch safety.
- When you want PR titles and bodies generated from branch tickets (e.g., ME-12345) or a provided title.
- When you require an integrated bugbot review workflow and structured feedback loop.
- When you rely on CircleCI checks and want a final, summarized PR status.
Quick Start
- Step 1: On a feature branch (not main/master), stage your changes (git add -A).
- Step 2: Trigger Avi Pr Flow to review, commit, push, and create/find the PR using your branch ticket or provided ARGUMENTS.
- Step 3: Let it handle bugbot review, poll CircleCI, and report the final PR status.
Best Practices
- Ensure you start from a clean working tree and stage all relevant changes (git add -A).
- Name your feature branch to include a ticket (e.g., ME-12345) for automatic PR titling.
- Run the /pr-review-toolkit:review-pr step before committing to address suggestions.
- Provide an ARGUMENTS title if you need a specific PR title; otherwise rely on the ticket-based auto-title.
- Monitor bugbot and CircleCI outputs; address issues promptly and re-run the flow as needed.
Example Use Cases
- ME-12345: add user authentication flow
- ME-54321: fix login crash on logout
- ME-98765: refactor chart rendering component
- ME-24680: optimize API response caching
- ME-11223: update README and docs links
