VibeBoot Doctor

No. The Doctor is plain JavaScript running in this page. It matches what you paste against the fixers' data in your browser. Nothing is sent, logged or stored.

They're the same 70 entries as the Next.js, Auth.js, Prisma and Stripe webhook fixers on this site, each reproduced or checked against the versions listed on its page (for example Next.js 16.4.5, next-auth 5.0.0-beta.32, Prisma 6.19 and stripe-node 23.0.0). The Doctor routes your paste to the best entry and links to the full write-up.

Only things the fixers already document: how next is pinned, next vs eslint-config-next, the Next.js 16 middleware rename, next-auth v4 vs v5, Prisma's generate step and prisma vs @prisma/client versions, and Stripe webhook verification. It doesn't guess about packages it has no data for.

Where a file in the free Cursor Rules Pack covers the problem, the Doctor links to it. Drop it in .cursor/rules and your agent stops writing that bug again. Where no rule covers it yet, the Doctor says so instead of inventing one.

Yes. Run npx github:vibeboot/vibeboot-doctor in your project folder. It runs the same checks on package.json, every .env file and middleware.ts, flags .env files committed to git, and matches errors you pass it or pipe in. It's MIT, has no dependencies, works offline and masks every secret value. Source: github.com/vibeboot/vibeboot-doctor.

Yes. Add the free composite Action: uses: vibeboot/vibeboot-doctor@main after actions/checkout. It runs the same scan on the PR checkout and exits 1 on a leak so the check fails. No secrets needed. Copy-paste workflow is on this page under Run it in CI, and in the GitHub README.

Paste the first line of the error plus a few lines under it. If it still doesn't match, it isn't in the data yet; try the individual fixer pages or the Next.js docs.