docs: document removal of --skip-generate and --skip-seed flags in Prisma 7

[AmanVarshney01]

…isma 7

Summary by CodeRabbit

• Documentation
  • Updated CLI reference documentation to reflect removal of --skip-generate and --skip-seed options in Prisma 7.
  • Added guidance on running Prisma generate and seeding explicitly for migrate dev and db push commands.
  • Expanded Prisma 7 upgrade guide with information about removed CLI flags and environment variables.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated Prisma 7 migration documentation and CLI reference to reflect the removal of --skip-generate and --skip-seed CLI flags. Added inline warnings notifying users that these flags no longer exist and guidance to run prisma generate and prisma db seed explicitly.

Changes

Cohort / File(s)	Summary
Prisma 7 CLI Reference content/200-orm/500-reference/200-prisma-cli-reference.mdx	Removed --skip-generate option from db push and migrate dev command tables; added inline warning blocks indicating these flags were removed in Prisma 7 and users should run prisma generate explicitly. Also removed --skip-seed from migrate dev with combined warning for both removed flags.
Prisma 7 Upgrade Guide content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx	Added documentation announcing removal of --skip-generate and --skip-seed flags with requirement to run prisma generate explicitly. Clarified that migrate dev and db push no longer auto-run Prisma Client generation. Expanded environment variables removal section with detailed list of deprecated PRISMA-related variables.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

These are straightforward documentation updates reflecting API changes. The modifications follow consistent patterns across files—removals paired with consistent warning blocks and guidance text. No code logic, dependencies, or structural changes to review.

Possibly related issues

• db push --skip-generate flag is gone in Prisma 7 #7373 — Directly addresses the reported missing documentation of the removed --skip-generate flag behavior in db push and migrate dev commands.

Possibly related PRs

• feat: add mention of mongo support coming for P7 #7271 — Updates documentation to reflect that explicit prisma generate calls are now required instead of automatic generation.
• DC-6434 Clarify prisma db seed is only run explicitly in v7 #7352 — Documents concurrent v7 change requiring explicit prisma db seed calls instead of automatic seeding.
• docs(): add v7 migration guide #7249 — Modifies the same v7 upgrade guide with overlapping changes to CLI flag removals and guidance.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: documenting the removal of two CLI flags (--skip-generate and --skip-seed) in Prisma 7, which is precisely what both modified files address.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[github-actions]

original	preview
content/200-orm/500-reference/200-prisma-cli-reference.mdx	content/200-orm/500-reference/200-prisma-cli-reference.mdx
content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx	content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx (1)

378-383: Tighten command naming + make the “what to run now” steps explicit

Consider:

• Using the fully-qualified commands consistently (prisma migrate dev, prisma db push) instead of “migrate dev / db push” (reduces ambiguity for skimmers).
• Adding the explicit follow-up commands inline (e.g., “Run npx prisma generate” and (for seeding) “Run npx prisma db seed”), ideally with links to the generate / seeding docs.

content/200-orm/500-reference/200-prisma-cli-reference.mdx (1)

1202-1207: Make the replacement action unambiguous (show the exact command)

Minor clarity tweak: instead of “Run it explicitly if needed”, consider spelling out the command users should run (e.g., “Run prisma generate explicitly if you need updated Prisma Client artifacts after db push.”).

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 44f03b7 and c3985dd.

📒 Files selected for processing (2)

• content/200-orm/500-reference/200-prisma-cli-reference.mdx (2 hunks)
• content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Fix internal inconsistency: migrate dev step list still says it generates artifacts

With this new warning, the earlier numbered list for migrate dev still states it “Triggers the generation of artifacts (for example, Prisma Client)” (Line 1370-1371), which is now contradictory. Please update that step (or add version-conditional wording) so the section is self-consistent.

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	c3985dd
Status:	✅  Deploy successful!
Preview URL:	https://51a05c3b.docs-51g.pages.dev
Branch Preview URL:	https://dr-6471-db-push-skip-generat.docs-51g.pages.dev

View logs