# Kirocrew Prepare PR

LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other...

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill kirocrew-prepare-pr -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill kirocrew-prepare-pr -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill kirocrew-prepare-pr -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill kirocrew-prepare-pr -g -a gemini-cli -y`

## Description

LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop, issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Prepare PR

Drive the working tree to a **merged PR**: open it review-ready, then keep driving
until CI and the review bots are satisfied and GitHub lands it. Opening the PR is
the midpoint, not the end. Every Kiro Crew author, maintainer or outside
contributor, runs this same loop, so it also states the repository's rules.
It is for the Kiro Crew repository only: in any other repository, ignore it.

This file carries only what the loop executes: which script to run and what its
exit code means. A script's flags live in its usage text, each CI lane's rules in
`references/ci.md`, and the reasons in `references/rationale.md` (read it before
deviating).

## Mode, decide once, at the start

| Signal in the request | Mode |
|---|---|
| Anything else, including ambiguity and a PR you opened incidentally | **Full loop** (default): ends by arming auto-merge and watching until it merges |
| An explicit stop: "update the PR", "push my changes", "sync my branch", "just update the body/description", "don't wait for CI" | **Prepare-only** |
| An explicit hold: "don't merge", "leave the merge to me", "review only" | **Full loop without auto-merge** |

**Precedence:** a stop signal wins only when it is the *whole* ask, "push this and
make it green" is the full loop. A hold turns off Phase 4's auto-merge, nothing else.

- **Full loop**, Phase 0 once, then Phase 1 → 2 → 3 until review-ready, then Phase 4.
- **Prepare-only**, Phase 0 once, then ONE pass of Phase 1 → 2 → push → a single `pr_status.py` snapshot → report → STOP. The Phase 2 gate still runs; a push always goes out locally-green. No server poll, no auto-merge.
- Say in one line which mode you picked, so the user can redirect.

**Never `gh pr merge` without `--auto`, and never bypass a required review or
check.** Auto-merge hands the merge to GitHub, which lands it only once the repo's
own required reviews and checks pass.

## Kiro Crew CI at a glance

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/builtin_skills/kirocrew-dev/kirocrew-prepare-pr/SKILL.md