10 questions to answer first.
Built your app with AI? Check what could expose user data, cause unexpected bills, or stop working when customers arrive. Copy the prompt into your AI tool to review your code and find out what to check or fix first.
Useful before launch or after you’ve gone live. A starting point, not a full engineering review.
Open your project in an AI tool that can read its code. Start a new chat and paste the prompt. It asks for a read-only report: what’s working, what needs checking, and which changes need a careful plan.
Reviews your code without changing it. Open the link at the end of the report, or paste it into your browser, to fill in your answers here.
Open the link from your AI report to fill in your answers, or mark them yourself: Looks good, Not sure, or Needs fixing. Change any answer the evidence doesn’t support. Not sure is useful: it shows what still needs checking.
Open “How to check” on a question for practical checks and a prompt to investigate it.
Your answers save in this browser. Email yourself a link to continue on another device.
These answers came from your AI report. Scroll up to change any you disagree with, and your next steps will update.
Changes involving sensitive data, payments, or live users benefit from a careful plan and another pair of experienced eyes.
On a free call, we’ll discuss what you built, your results, and whether a paid review would help.
Book a free 15-minute call to discuss your app →With Laura directly · Prefer to message first? DM “audit” to @lauraq.dev.
There’s more to review than launch risks, including your user experience, performance, and costs. See what an independent review adds.
Start with the first item in your results. Your next steps are grouped as Safe to try with AI, Check before changing, or Engineer review recommended. Check the evidence and work on one issue at a time.
If your report recommends a more cautious path, follow it. If it says a change marked for engineer review here is safe to try with AI, use the verify prompt before changing anything.
This page uses your answers to suggest next steps and default urgency; it does not read or validate your AI report. If the report gives a different urgency and explains why, follow it after checking the evidence it cites. If the consequences or recovery are unclear, verify first.
Asks your AI to plan one fix and stop for review if the change could affect live data, access, or payments.
Ask for evidence before relying on a claim that something is safe.
A code review is only part of the picture. Try these checks before launch, or repeat them on your live app.
A fresh account helps you see the experience without your saved settings, permissions, or familiarity with the app.
Check that sign-up and password-reset emails reach an address outside your team. Reading the code alone won’t confirm delivery.
Careful: Sending from your own domain means adding records to it. If you already get email at that domain, like a Google Workspace inbox, have someone check the records first so you don't break it.
I’ll email you a link back to this checklist so you can finish later. If you’ve completed all 10 questions, the email will include your results too.
Your answers are saved in this browser. To improve this checklist, I count anonymous totals, like how many people marked payments “Not sure”. Those totals are never linked to you or your email. Your email is used only to send this checklist unless you separately subscribe.