contributing-to-loopoverlisted

# Contributing to LoopOver — the one-shot PR playbook LoopOver merges through an **automated, one-shot review**: the loopover gate (a GitHub App that posts a check run + a single review verdict) and a **strict CI suite gated by Codecov**. There is no human ping-pong and no "fix it in review" — **the PR must be perfect before you push.** This skill is the end-to-end procedure to make that happen with AI tools (Claude Code / Codex). Work through the phases **in order**. Do not skip the verification phases. If you cannot get the full local gate green, **do not push** — an incomplete PR will be auto-closed or held, not coached. `reference.md` (next to this file) has the exhaustive tables (every CI job, the full Codecov rules, the gate config, the MCP tools, test helpers, the commit/PR rubric). Read it when a phase says to. --- ## What the gate does to your PR — it merges and closes, automatically LoopOver's review engine has **real autonomy** here — it is **not advisory**. Within ~2 minutes of your PR's checks settling, for a **contributor** PR (you are not the repo owner or an automation bot) it takes a one-shot disposition: | Situation | Engine action | |---|---| | Review-agent check passes **and** every CI check green **and** mergeable-clean (+ approvals) | **auto-approve → MERGE** | | **Any** CI check failed — required or not, **`codecov/patch` included** | **CLOSE** (one-shot) | | Gate **failure**, or base **conflict** (needs rebase), or a linked-issue **hard-rule** v