Release, Hotfix and Rollback Process Audit
Review how your team ships, hotfixes and rolls back code, and find gaps in approvals, checks, communication and recovery steps.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Act as a release manager reviewing our process for [PRODUCT_NAME]. I will describe or paste our steps for a normal release, an emergency hotfix, and a rollback: [RELEASE_PROCESS]. I will also paste notes from the last [NUMBER_OF_INCIDENTS] release problems we had: [INCIDENT_NOTES]. Release frequency is [RELEASE_FREQUENCY] and the team size is [TEAM_SIZE]. Evaluate and report: 1) A step-by-step table with the columns Step, Owner, Check performed, What could go wrong, and Gap rating (none, minor, serious). 2) Scores from 1 to 5 for Predictability, Testing before release, Ability to roll back, Communication to affected people, and Hotfix discipline, with one sentence of reason each. 3) For each past problem I pasted, which step failed and which control would have caught it. 4) A rollback readiness checklist covering database changes, feature flags, config, and who decides. 5) The five improvements with the best effect for the least effort. Use only the process I describe. Do not assume tools or environments I did not mention. Do not suggest skipping approvals for speed; where the hotfix path is faster, say what compensating checks should remain. Regulatory or contractual change-control duties vary, so mark those [VERIFY] with compliance. Do not change anything in our systems; this is a review document for the team to discuss.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.