Cursor's agent mode will build a whole feature across a dozen files while you watch. After a few weeks of that, your repository holds the work of fifty sessions that never saw each other's code.
I read the codebase as a whole, not one chat at a time. You get a ranked list of what to fix, in plain English, with a fix prompt for each finding that you can paste back into Cursor.
1Line 7: Whatever the request sends is written to the row, including ownerId, plan and every other column on the model; the zod schema in lib/validation.ts was never wired up here.
Common problems in Cursor apps
Not every app has all of these. The report tells you which ones yours has, where, and what to do about each.
Critical
API routes that forgot to ask who is calling
A route added in one session copies the shape of its neighbors but not their auth check. I find every Next.js route handler, server action and Express endpoint that reads or writes user data without verifying the session.
High
Request bodies written straight to the database
Handlers that take req.json() or a server action argument and pass it to Prisma as the update payload. A zod schema exists somewhere in the repo; it was never applied here. I list each unvalidated entry point and what a caller can change through it.
High
Casts added to make the red squiggles go away
When the agent hits a type error it often reaches for as any, as unknown as or @ts-ignore instead of fixing the type. Each one is a place where TypeScript has stopped checking. I rank them by what they hide.
Medium
Refactors that stopped halfway
A session that renamed a module or swapped a library ran out of context before it finished. Old and new versions both live in the codebase, and which one runs depends on which import a file happens to use.
Medium
Tests that cannot fail
Test files that mock the function under test, or only assert that the mock was called, pass green on every commit. I tell you which tests check something real and which are decoration.
Low
Three versions of the same helper
formatDate in utils, lib and the component folder, each slightly different, because each session was told to make it work and did not look around. I map the duplicates and say which one to keep.
Treatment plan
How it works
1
Book a check-up
Choose a tier and tell me where to send the report. Add your app's address if it is live. Two minutes, no sales call.
2
Show me your code
Pay by card, then give me read-only access to your code on GitHub (you paste in a key I send you) and let me into your app with test accounts. Never done that? I send you step-by-step instructions for your tool. I measure your app and confirm it fits before I start.
3
Get your diagnosis
Ready to launch, or not yet. Problems ranked, critical ones proven on your live app, each with a prescription for your AI tool. A PDF by email, then 7 to 30 days of questions by email.
4
Fix it, then a free follow-up
Fix the problems yourself, with your AI, or let me do it with the Fix Pack. Tell me within 30 days and I check once more that they are really gone.
No idea how big your app is? That’s normal, and you never have to count anything. Book the review you want; I measure your app before I start and tell you. If it doesn’t fit, you choose: upgrade, narrow it down, or a full refund. “Lines of your code” means the code you and your AI wrote, not the packages and UI kit your tool installed; many apps built with Lovable, Bolt or v0 fit the Safety Scan.
Start small, upgrade later. The Safety Scan’s price counts in full toward a Launch Review or Fix Pack for the same app within 30 days of your report.
Why this price? Software does the first pass, so you pay for the part only a person can do: checking every finding in your code, proving the critical ones and deciding what matters for your app. I take at most 3 Safety Scans and 2 Launch Reviews (or one Fix Pack) a week; if this week is full, yours starts the next.
Prices in US dollars, paid once, no sales call and no surprise invoice: anything extra is your choice, told to you before I start. The clock starts when I can see your code. Reports arrive as a PDF by email, in English, or German if you prefer.
Need a few things fixed after a scan? I fix by the hour at $199, three hours minimum, with the list agreed before I start.
Bigger than 50k lines, or a real mess? Rescue jobs are quoted, from $3,000, no obligation. Email me.
Not for you if
you have a team of engineers who already review each other’s code,
your app’s backend isn’t JavaScript or TypeScript (Python Replit apps, for example), or it is over 100k lines,
you handle regulated data (health records, banking, children), or need a pentest, certificate or compliance sign-off. Taking card payments through Stripe is fine.
A review lowers your risk a lot. It can’t guarantee that your app is secure, and nobody honest will say otherwise.
Cursor questions
How do I share code written in Cursor?
Cursor works on a normal local project, so push it to a GitHub repository (or GitLab or Bitbucket) and give me read-only access (I send you a key to paste in; it takes a minute). If it is not in version control yet, now is a good time, and I can walk you through it.
Can I apply the fixes in Cursor?
Yes. Each finding comes with a fix prompt written for an agent, naming the files and the exact change. Paste it into Cursor chat or agent mode, read the diff before you accept it, and run the tests.
Do you need my chat history or Cursor rules?
No. I review the code in the repository, which is what runs in production. If you have a .cursorrules file, a .cursor/rules folder or an AGENTS.md I will read it, because the report ends with rules to add so the next session does not reintroduce the same problems.
Why not just ask my AI to review it?
Do, and I will even give you the prompt. You will get a long list. What your AI cannot do is tell you which items are real, prove them against your live app, see your database and hosting settings, or check that its own fixes worked. If you cannot read code, that is the part you cannot do yourself either. It is what you pay me for.
I'm not a developer. Is this for me?
Yes, that is exactly who it is for. If you built an app with AI and cannot tell whether the code is any good, I check it and explain what matters in plain English. You never need to understand the code to act on the report: every problem comes with a prompt you paste into your AI tool. And you do not need to know what to ask. The report answers the questions you would have asked if you knew how.
How do I show you my code?
Most AI builders can push your app to GitHub, a free site that stores code. You give me read-only access by pasting a key I send you into your repository settings, which means I can look but not change anything. Never done it? After you book, I send you step-by-step instructions for your tool. A zip file works too. When the report is delivered, remove my access again; I remind you.
Is my code safe with you?
Every booking comes with an NDA, automatically. I never sell, publish or pass on your code. The only other party that sees it is the AI provider that helps with the first pass, under terms that do not allow it to train on your code. I never need your passwords or your live database, and I delete my copy within 7 days of delivering the final report.
From $149 for the first 10 customers (10 left). Ready within 2 business days. If the Safety Scan finds no problem rated medium or worse, you pay nothing.