ship

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Ship

A pull request is ready when the human can merge it without asking anything. Green checks in CI, not on this machine, are the bar.

## Prepare

The branch holds only durable work: temporary artifacts such as specs, prototypes, and reports stay out of it. When the work came from a spec, check that what must outlive it is in the change, not only in the spec. Bring the branch up to date with its base, and rerun the project's gates when that changed anything.

## Open

Push the branch and open the pull request as a draft against its base, with the title and description written by `pr-description`. It stays a draft: the human marks it ready for review once they have looked at it.

## Drive checks to green

Watch every CI check until it finishes. For each failure, find why it fails in CI when it passed locally, such as a different platform, browser, path, timeout, or concurrency, fix the cause, and push again. A check that passes only on a retry is flaky, not green: diagnose it with `diagnosing-bugs`. Make checks pass by fixing code, tests, or configuration; disabling a check or weakening a test to get green does not count. When a failure is outside the change, show that it fails on the base too, say so in the pull request, and find or open its issue so the next delivery inherits the diagnosis. When a fix changes what the description says, update the description with `pr-description`.

When a failure needs something you cannot get, such as a secret, infrastructure access, or a human decision, stop and name it.

## Done

Every CI check is green, the description matches the final state, and the draft pull request is ready to merge once the human marks it ready for review. The human marks it ready and merges.

From taecontrol/skills, MIT.

More from taecontrol/skills