pr-to-greenlisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> > 🤖 *Auto-generated by **weekly-pattern-learner** · ci-fix-loop, coderabbitloop, and qodoloop all exist independently: no skill orchestrates them into a single end-to-end 'drive PR to green' pass* # PR to Green Drive a GitHub PR from first push to fully merge-ready: CI checks green, every active AI review bot addressed, zero unresolved threads. ## Inputs - **PR number** (optional): detect from current branch if not given. - **Max total iterations** (optional, default: 10): across all loops combined. - **Skip bots** (optional): `--skip-qodo`, `--skip-coderabbit` to limit which review loops run. ## Phase 1: Ensure the PR exists ```bash gh pr view --json number,headRefName,state 2>/dev/null ``` If no open PR exists, run `olko:pr-description-writer` first to create one, then continue. ## Phase 2: CI fix loop Run `olko:ci-fix-loop` until all required checks pass, or a blocker needs a human. Check current state first: ```bash gh pr checks --json name,state,conclusion \ --jq '.[] | select(.conclusion != "success" and .conclusion != "skipped")' ``` If all checks already pass, skip to Phase 3. Otherwise run `olko:ci-fix-loop`. **Stop entirely if ci-fix-loop returns `blocked`**: do not run review loops while CI is red, as bots may refuse to review a failing branch and their feedback will shift after fixes land. ## Phase 3: Detect active review bots ```bash # Check if Qodo has posted on this PR gh