home/roleplay/must-fix-before-apply

Must Fix Before Apply

GPTClaudeGemini··1,288 copies·updated 2026-07-14
must-fix-before-apply.prompt
Review the selected migration plan and code for production safety.

Focus on forward compatibility, rollback feasibility, data integrity, and operational risk.
Assume a live system with concurrent reads and writes.

Output exactly in this format:

## Must Fix Before Apply

List migration blockers.

For each item:

- file/section
- failure mode in one sentence
- concrete safe fix

## Should Fix Soon

List non-blocking risks with meaningful impact.

## Rollback Plan Check

- rollback feasible: yes | no | partial
- missing rollback prerequisites
- specific rollback procedure recommendation

## Zero-Downtime Check

- compatible with old and new app versions: yes | no | partial
- lock/contention risk: low | medium | high
- required phased rollout steps

## Test Gaps

List missing migration tests (forward, backward, data invariants, load-sensitive paths).

## Final Recommendation

- apply now | apply after fixes
- biggest remaining risk in one sentence

when to use it

Community prompt sourced from the open-source GitHub repo eschaar/vstack (MIT). A "Must Fix Before Apply" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

roleplaycommunitygeneral

source

eschaar/vstack · MIT