Review every change since my last release before shipping
A pre-release review of all changes since a tag: missing translations, simplifications, breaking changes, security, and a draft changelog.
The prompt
Review everything that has changed since my last release so I can ship with confidence.
Last release tag or commit: [e.g. "v1.0.3"]
Changes: [PASTE the output of `git log --oneline <tag>..HEAD` and the diff, or give access to the repo]
App type and stack: [e.g. "React Native app", "Django web app"]
Supported languages: [e.g. "English and Turkish", or "English only"]
Areas I'm most worried about: [e.g. "payments", "database migrations", "login"]
Use the commit messages to understand the intent of each change, then check:
1. Localization: hardcoded user-facing strings; keys added to one language file but missing from others; layouts that break with longer translations, plurals, or right-to-left text.
2. Simplification: duplicated logic, styles, or components that could be merged; dead code, unused imports, leftover debug logs, and feature flags ready to remove.
3. Correctness: empty and null states, error handling, race conditions, off-by-one errors.
4. Breaking changes: API contracts, migrations (reversible? safe on large tables?), new config or environment variables, compatibility with older clients.
5. Security: secrets in code, unvalidated new inputs, missing permission checks.
6. Tests and docs: changed behavior without tests; README, changelog, or docs not updated.
Return:
- A findings table: File | Issue | Severity (blocker / should fix / nice to have) | Suggested fix.
- Patches for blockers and straightforward fixes. Ask before any larger refactor.
- A draft changelog grouped into Added, Changed, and Fixed.
- A go/no-go recommendation with reasons.
Don't claim you reviewed a file you didn't see. List anything you couldn't check.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- e.g. "v1.0.3"
- e.g. "React Native app", "Django web app"
- e.g. "English and Turkish", or "English only"
- e.g. "payments", "database migrations", "login"
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Get a beginner-friendly code review of my first projectA ranked set of the five improvements that matter most, explained simply, plus what you did well and what to learn next.
- Audit the developer experience of my software package or APIA structured review of your docs, onboarding, community signals, and competitor position, with a prioritized list of developer-experience fixes.
- Restyle a UI component to match a reference designRefactor a component's markup, styles, and accessibility to match a design-system reference while keeping its props, state, and logic intact.
- Diagnose slow launches and API cold starts in my mobile appA codebase-specific diagnosis of startup time, serverless cold starts, and network waste, with fixes ranked by impact on perceived speed.