patpat-ship

Patpat Ship

Before following this skill, apply the skill state and mutation gate.

When invoked directly, read the operating protocol and execution graph in full. Do not load the router.

Read preserve safety and proof over proxy.

After verify and review pass, require delivery intent: explicit commit, PR, or ship language; overnight or continuation; or explicit land or merge. Explicit /patpat activation alone is not delivery authority. Also require that no higher-priority repository rule forbids delivery. Then apply default delivery: commit the in-scope diff, use a non-force push, and open or update one ready pull request unless the user opted out or the path was read-only.

Apply authorized delivery to merge, publish, or deploy. Only explicit land or merge language authorizes merge. Overnight, going to bed, or don't stop drives a verified pull request to merge-ready and stops. Do not land a real CI failure. Retrigger an infrastructure flake at most once, only within existing delivery authority for that pull request, and never by pushing an empty commit or rerunning a job that deploys, publishes, or writes externally. A repeated failure earns no further retrigger; inspect its job logs and reclassify.

Patpat prescribes no CI system, job list, or duration. CI belongs to the project: at ship time, read its policy, configuration, and recent runs, then decide which checks prove this change and how long to wait, scaling local checks to the change's risk and to what changed since the last proof. Project instructions and the user's stated preferences are inputs to that decision. Follow what the user asks for: add or tune CI when they request it, and suggest a gap rather than adding it unasked. A failing optional check is still evidence: explain it, and it still stops a Patpat merge. Scaling chooses which checks to run; every check relied on must run at the exact head or pass the durable gate, as patpat-verify defines. The gates in the delivery playbooks stay fixed: never claim a check that did not run, and never weaken a check on your own initiative. If the user asks to relax a required check, apply the pause in preserve safety and wait for their confirmation. Relaxing a policy does not waive a real failure on this head.

For CI monitoring or PR readiness work, use PR Readiness Handoff. It is the canonical source for GitHub observation, native stack discovery, watcher budgets, stale handling, and authority boundaries.

Consume durable state when it exists. Delivery proof defines what binds a commit, which gate each delivered head uses, and how slices and whole programs differ. A failed gate stops delivery; a passed gate grants no authority.

Inspect version-control state, unrelated dirty files, and secrets before any git write. Workers never ship. Re-check the remote revision after the action.

Pause for production deploy, package publish, force-push, secret rotation, and risky auth, billing, or permission changes. Explain blast radius, rollback, and verification before continuing.