Development

/pr-loop

Invoke before any git/gh or agent dispatch: open a PR, merge, ship, CI, full-stop/READY UNMERGED. Signs: 🤖 model + harness line, Co-Authored-By.

$ golems-cli skills install pr-loop
46 evals
fixtures

Updated 6 days ago

Fleet law: canon #2 owns branch→commit→push→PR→review→merge and PR URL validity. This skill owns the procedural loop, review handling, edge cases, and worker-vs-lead endpoint mechanics.

Kickoff contract

  • Claude seats: invoke /pr-loop with the Skill tool before the first PR action of a lane: opening, updating, merging or shipping a PR, or fixing red CI. Make it the first tool call, before any git/gh/grep orientation: live misses open with git status/gh pr and never load the skill (PR15 trigger eval, 2026-10-19).
  • Codex seats: read this SKILL.md body (a file read) before that action; Codex has no Skill tool.
  • A lead's kickoff brief to a worker names the skills the worker invokes (/large-plan, /agent-routing, /pr-loop).
  • Standing ask: "Once its PRs land, invoke the updated skills at the start of each plan, dispatch or PR action." (Etan 2026-10-18, via orc collab)
  • Why: Claude T3 leads made 0 Skill calls on Oct 16–18 while all three lead skills sat in their catalog (skill-edits audit, 2026-10-18).

Ownership

Who implements and who opens the inner-loop reviewer pane is owned by /agent-routing § Routing rules (SSOT). Never start that reviewer yourself unless that routing law makes you the owner.

Every Codex dispatch in this loop (short seats, no waiting inside a turn, no task that is only reading or running scripts or tests, effort caps, the daily count) follows /agent-routing § Codex seats.

This skill begins at branch preparation and ends at the authority-appropriate endpoint:

  • Lead, when the endpoint permits merge: reviewed, latest-head-green PR merged, verified, root checkout fast-forwarded, and cleaned up; released/installed where applicable at the feature-batch gate, without asking Etan.
  • Worker whose brief says the lead owns merge: ready-for-review PR, review responses addressed, URL handed to the lead, unmerged.
  • A worker must hand the reviewed PR to its lead unmerged.

Run scripts/ci/release-gate.mjs <repo> at the feature-batch gate, not after every PR. At the batch endpoint, MERGED_UNRELEASED, RELEASED_UNINSTALLED, or UNKNOWN is a stop; release/install and rerun until CLEAN. A MERGED_UNRELEASED mid-batch is expected, not a stop: keep merging the batch.

Full stop endpoint

Select full stop for a PR-workflow “full stop” command, an explicit no-merge request, or a third-party upstream base (for example, pingdotgg/t3code). Emphasis (“Full stop.”), quotations and questions about the phrase do not select it; read-only inspection does not start PR preparation. This endpoint overrides generic ship/merge rules for every role and survives handoffs and watch wakes until the user explicitly changes it. Confirm the live PR base, not the fork remote; see full-stop rules. Never merge, enable auto-merge, enqueue, push the default branch, or delegate those actions. Before work and each push, verify auto-merge/queue state; disarm only this account’s enrollment or our own PR’s setting we control, otherwise stop BLOCKED before a push that would merge. Keep the normal proof, draft-first, lead-routed review and latest-head checks. Finish with READY UNMERGED, WAITING FOR MAINTAINER APPROVAL (only a verified upstream human-approval requirement remains), or BLOCKED; use the readiness and handoff contract. Terminal readiness ends PR preparation unmerged; it is not a held draft or release/install/LIVE proof.