Branch Finish Checklist

Branch Finish Checklist reads your specific diff and context — stack, what changed, what you've already verified — and returns a targeted pre-merge checklist derived from that change, not a static template. An API change triggers a consumer impact review and a docs sync check. A migration triggers forward-run and rollback verification steps. A new environment variable triggers a deployment docs audit. The output is scoped to what your branch actually touched, so nothing generic and nothing missed.

You give it: your branch summary (the migration adds a nullable column to the orders table, backfilled in chunks), your stack (Rails 7, PostgreSQL, Heroku), and what you've already done (ran tests locally, confirmed migration runs in staging). It asks four short clarifying questions if anything is ambiguous, then builds the checklist from that diff-specific picture.

The output is structured and verifiable: a Leftover Audit (any debug logs or commented-out code to clear), a Migration Rollback Check (confirm down migration tested at production row count, not just staging volume), a Docs & Changelog item (API response shape changed — update internal docs and notify consuming teams), and a CI gate item (confirm no test was skipped or marked pending to get green). Every item has a concrete verification condition, not just a label.