← ClaudeAtlas

open-prlisted

Create a PR from your local changes, then run the automated review loop on it. Branches, commits, pushes, opens the PR with `gh pr create`, and launches the reviewer-fan-out + classify + fix loop. The loop notifies you when the review is clean; merging stays yours. Run `/review-pr setup` first.
buddhikernel/buddhi-review · ★ 1 · Code & Development · score 73
Install: claude install-skill buddhikernel/buddhi-review
# /open-pr — create a PR, then review it **Buddhi lands your PRs.** This skill gets a PR airborne — branch, commit, push, open — then flies the automated review rounds; once review is clean it is ready to land (merge) on the base branch. ## Critical behaviour rules - **Only sanctioned interactive gates, otherwise silent.** The ONLY questions you may ask are the **first-run onboarding** prompt (Step 0, only when this machine has no config), the **per-repo reviewer confirmation** prompt (Step 1.1, only when this repo's reviewers are unconfirmed), the **target-selection** prompt (Step 1.5), and the **pre-launch rebase** prompt (Step 2) — and the last two ONLY when the engine reports an ask is needed (`present.ask == true`, or a non-clean rebase status). Everything else runs silently. - **NEVER pause for confirmation** between any OTHER steps. Run them back-to-back. Never ask the user what to do on error — log it and stop. - **Reviewers trigger based on the fleet confirmed for THIS repo** (per-repo, because the vendor GitHub Apps + the claude workflow are installed per repo; set via the Step 1.1 terminal setup wizard or `/review-pr setup`, stored under `repos:` in `~/.config/review-loop/config.yaml`), falling back to your global default, then the built-in Copilot/Gemini/Codex/Claude set. If a reviewer is not responding, confirm reviewers for this repo (Step 1.1) or run `/review-pr setup`. Do not assume any specific reviewer is auto-triggered. - **NEVE