patpat-ship

Commit and open or update a ready pull request after verified work when delivery intent exists, and merge only with explicit land or merge language. Use at the end of an active Patpat implementation a

SKILL.md

GitHub

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. Retry a flake once.

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.

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.

Proof closure

Close repository mutations through: