DEPLOY HANDOFF

Your PR merged. Did the production setup move with it?

A code review can miss the work outside the code. DeployDoctor compares the PR merge base and head, then turns supported deployment changes into a checklist you can hand to your teammate or coding assistant.

What the checklist covers

• New environment references: review whether each name is required or optional and configure the target environment securely.
• Migration files: review deployment order, staging and recovery before changing a database.
• Hosting configuration: inspect changed committed settings for Vercel, Cloudflare, Netlify, Fly.io, Render and other supported configurations.
• Production commands: verify changed package build/start hooks with the actual deployment environment.
• Endpoint source changes: test callers, callbacks and webhooks affected by supported Next.js route-file changes.

Evidence you can follow

Every task links to its file at the compared commit. Copy the complete Markdown checklist into a release issue, PR conversation or your coding assistant. Configuration values and raw build commands are not included in this inventory.

How to use it

1. Paste a same-repository GitHub pull request URL into the existing scanner.
2. Run the PR comparison with the default build and environment categories. Existing scan allowances and private-repository permissions apply.
3. Open Deploy Handoff in the saved report, copy the checklist, and verify each step in your real deployment environment.

A manual handoff, with explicit limits

Tasks are not automatically complete. New references can be optional or development-only. A text change is not proof of changed runtime behavior. Partial scans remain review candidates; dynamic references, unsupported paths and live provider settings are outside coverage. Builds, migrations, checkout and live health checks are never run by this feature.

Existing reports need a new PR scan to obtain the inventory. Fork PR comparison remains unsupported. Reports and copied checklist text can contain repository paths and variable names; share private checklists only with authorized people.

Use the existing PR workflow → · Exact scanning coverage → · Existing passes and private scanning →