auto-pr

Automates the full SDLC pipeline from planning through pull request and review loop.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill auto-pr-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-pr
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/auto-pr
Command: npx skills add https://github.com/bravros/bravros --skill auto-pr-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually coordinating planning, implementation, PR creation, and code review cycles across a software change is slow and error-prone. This Skill runs the entire pipeline autonomously from a single command, producing a merge-ready pull request without user intervention. ## Core Features & Use Cases - Autonomous multi-stage pipeline: Delegates through recon, orchestration, PR creation, and a review loop, all in unattended mode with zero user questions. - Enforced merge safety: Writes a lock file that blocks any direct merge to main, requiring an out-of-band token through the promote path, and caps review cycles at three. - Worktree isolation: Optionally runs the pipeline in a disposable git worktree so parallel autonomous runs never touch the main working directory. - Use Case: A developer types /auto-pr on a feature request; the Skill plans the work, implements it in an isolated worktree, opens a PR, triggers an AI code review, applies fixes from the verdict, and reports READY or BLOCKED. ## Quick Start Type /auto-pr with a description of the change you want, and let the pipeline plan, implement, open a pull request, and iterate on review feedback autonomously.

Frequently Asked Questions about auto-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a fully autonomous plan-to-PR pipeline?▼

Invoke /auto-pr explicitly with your change description. The Skill locks the run with bravros autopr preflight, delegates through recon, orchestrate, and PR stages, then runs a review loop until the PR is merge-ready or blocked.

How does the automated PR review loop work with GitHub?▼

The loop posts an @claude review request on the PR requiring a plain-text BRAVROS-VERDICT: approved or changes-requested line, then polls gh pr view every ~60 seconds for up to 30 minutes. A changes-requested verdict triggers fix agents and a re-trigger, up to 3 cycles.

Can auto-pr merge directly to the main branch?▼

No. Direct merges to main are blocked by the .auto-pr-lock written at preflight, which closes the bravros police staging lane. The only merge path is /promote with an out-of-band token cleared by the operator from a separate terminal.

What happens if the AI review posts no verdict marker?▼

The pipeline fails closed and halts rather than guessing a verdict. The operator must run bravros pr-review unlock from a separate terminal, then bravros pr-review with --write-stamp, since the running session cannot authorize its own merge.

When should I use the --worktree flag with auto-pr?▼

Use --worktree when running parallel autonomous pipelines or when you want isolation from the main working directory. It creates a disposable git worktree via bravros worktree setup-full, and cleanup refuses while live processes remain inside it.