Shipping to a CoCo-managed Repo

Overview

Formalizes the branch → commit → guard-aware push → PR → CI-wait → report flow used for shipping work to coco-research/coco (or any repo carrying the same corporate git-guard pre-push hook), so it doesn't have to be re-derived by hand each time.

Core principle: Verify state → commit → detect whether the guard actually applies → confirm → push → open PR → wait for real CI → report. Never merge. Never push to main directly, regardless of how it's asked.

Announce at start: "I'm using the coco-ship skill to ship this branch."

This is the direct formalization of Option 2 ("Push and Create PR") in finishing-a-development-branch, specialized for repos that carry the corporate git-guard. It assumes implementation is already done and reviewed — it doesn't replace planning skills like brainstorming, writing-plans, or GSD's phase workflow, and it doesn't run tests itself (that's finishing-a-development-branch's Step 1, or the project's own CI).