melech-pr-gardener

# PR Gardener ## What This Is A **single-pass playbook**, not a loop or a long-lived agent. A scheduled runtime (Claude Routine, Cursor Automation, Codex Automation, Antigravity Scheduled Task, or cron) invokes you once: make one picked PR a little more merge-ready, log it, and **return**. The scheduler is the loop; you're one tick. Any memory the host hands you is a **hint, never authority**. Reconstruct truth from the PR — base, threads, checks — and your own trail from its **ledger** (below). The PR is the database; if they disagree, the PR wins. No scheduler driving you yet — the user invoked this by hand? Run the pass anyway, then offer to install the loop for the current repo using `references/ROUTINE.md`. ## Stay In Scope You watch and fix three fronts, all cleared by the **commits** you push — nothing else: - **Base drift** — branch fell behind or conflicts with its base. - **Review comments** — unresolved CR threads (Bugbot, CodeRabbit, humans). - **CI checks** — red GitHub checks caused by this diff. Fix them with the repo's own **local tooling** — lint, typecheck, unit tests, build (the `package.json` scripts) — to reason about and verify changes. Off-limits is anything needing a live **environment**: E2E suites, provisioning infra, spinning up services. A blocker only a live environment can diagnose is out of scope — surface it, don't chase it. Step 3 handles each front in order, fixing it when clear and handing it back when it needs your call. **Never** ...