Ship a finished branch

Sync, test and land a ready branch with a PR body that lists what was run, the risks, and rollback steps.

Run it as a prompt

Paste this into any AI agent, or fetch it: curl -s https://uplift.page/api/v1/prompts/ship-a-branch-checklist/raw

prompt.md

# Ship a finished branch

Land a branch that is ready: up to date, tested, and with a PR a reviewer can approve quickly.

## Context
- Base branch: [BASE BRANCH]
- Branch to ship: [BRANCH NAME]

## Steps
1. Summarise what changed from the commit log and the diff against the base: features, fixes, migrations, config and dependency changes.
2. Bring the branch up to date with the base, using whatever the repo already does (rebase or merge). Stop and report if a conflict touches logic you do not understand.
3. Find the repo's own test, lint and type-check commands (package scripts, Makefile, CI config) and run them. Do not invent a new test setup. If the repo defines no type-check, run the language's standard one (for example `npx tsc --noEmit`) and say you did.
4. Fix failures caused by this branch. If a test also fails on the base branch, report it instead of fixing it here.
5. List the risky areas (migrations, auth, payments, public APIs) and run or add one targeted smoke test for each.
6. Write the PR: title under 70 characters; body with Summary, Why, Test plan (what was actually run and the result), Risks, and Rollback steps.
7. Show the summary and test results, and push and open the PR only after a go-ahead. After opening, confirm the PR's CI checks are green and report them.

## Rules
- Never force-push a shared branch, skip hooks, or disable tests to get a green run.
- Never commit secrets, .env files, or build output.
- If something blocks shipping, stop and list each blocker with the smallest fix.

## Output
A checklist of what was done with a one-line result per command, the ready-to-paste PR title and body, and any blockers.

The full prompt

Land a branch that is ready: up to date, tested, and with a PR a reviewer can approve quickly.

Context

Base branch: [BASE BRANCH]
Branch to ship: [BRANCH NAME]

Steps

Summarise what changed from the commit log and the diff against the base: features, fixes, migrations, config and dependency changes.
Bring the branch up to date with the base, using whatever the repo already does (rebase or merge). Stop and report if a conflict touches logic you do not understand.
Find the repo's own test, lint and type-check commands (package scripts, Makefile, CI config) and run them. Do not invent a new test setup. If the repo defines no type-check, run the language's standard one (for example npx tsc --noEmit) and say you did.
Fix failures caused by this branch. If a test also fails on the base branch, report it instead of fixing it here.
List the risky areas (migrations, auth, payments, public APIs) and run or add one targeted smoke test for each.
Write the PR: title under 70 characters; body with Summary, Why, Test plan (what was actually run and the result), Risks, and Rollback steps.
Show the summary and test results, and push and open the PR only after a go-ahead. After opening, confirm the PR's CI checks are green and report them.

Rules

Never force-push a shared branch, skip hooks, or disable tests to get a green run.
Never commit secrets, .env files, or build output.
If something blocks shipping, stop and list each blocker with the smallest fix.

Output

A checklist of what was done with a one-line result per command, the ready-to-paste PR title and body, and any blockers.

Served from the uplift.page library and refreshed within 5 minutes of every update.