Shipping Changes

Safely carry reviewed work from pull request through merge and deployment — pinning the exact head that passed, monitoring the exact post-merge run, applying migrations before an automatic deploy, verifying deployed identity, separating artifact trust domains, and interpreting skipped, queued, absent, or cancelled work honestly. Use when opening, updating, merging, or auto-merging a pull request; deploying to production; changing a schema; diagnosing a green merge that did not ship; designing deployment automation; or claiming which commit is live.

harshnag Updated

File contents

harshnag/agent-engineering-practices commit 89b603c495

Frequently asked questions

npx get-skill add harshnag/shipping-changes