home/roleplay/reviewer-post-release-audit

Reviewer Post Release Audit

GPTClaudeGemini··▲ 1,060 copies·updated 2026-07-14

reviewer-post-release-audit.prompt

<!-- Orchestrator contract:
  role: reviewer
  reads: [RELEASE_PLAN.md, RELEASE_LOG.md, SMOKE_RESULTS.md, DIFF_REVIEW_NOTES.md, RISK_ACCEPTANCE.md]
  writes: [POST_RELEASE_AUDIT.md]
  never_writes: [RELEASE_LOG.md, SMOKE_RESULTS.md, ROADMAP.md]
  produces: [STEP_RESULT.json]
-->
# Hotfix 05 — Reviewer Post-release Audit

You are in Reviewer mode performing the mandatory post-release audit for a hotfix.

Resolve active slice from ROADMAP as `changes/<slug>/`.

Goal:
Confirm the release evidence is complete and decide whether the hotfix can be considered closed.

Check:
- release plan and execution line up
- smoke results are credible
- any emergency override is justified and documented
- follow-up work is captured if the hotfix left debt behind

Write `POST_RELEASE_AUDIT.md` with verdict:
- `Closed`
- `Follow-up required`

## Output checklist
- [ ] `changes/<slug>/POST_RELEASE_AUDIT.md`
- [ ] `changes/<slug>/STEP_RESULT.json`

## STEP_RESULT.json (required)

when to use it

Community prompt sourced from the open-source GitHub repo kylehuirevvision/repo-rails (MIT). A "Reviewer Post Release Audit" 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.