docs(generators): add community generators from Lexmata and PegasusHeavy

[quinnjr]

Summary

• Add @lexmata/prisma-ent-generator — generates Go Ent schema files from Prisma schema
• Add @lexmata/prisma-python-generator — generates Python Pydantic model classes from Prisma schema
• Add @pegasusheavy/nestjs-prisma-graphql — generates NestJS GraphQL types from Prisma schema, ESM-first with Prisma 7+ support

Test plan

• Verify links to GitHub repositories resolve correctly
• Confirm descriptions are accurate and consistent with the existing list format
• Check that the docs site renders the new list items correctly

Summary by CodeRabbit

Documentation

• Added three new community generators to the reference: Prisma Ent Generator (for Go schemas), Prisma Python Generator (for Python Pydantic models), and NestJS Prisma GraphQL (for NestJS GraphQL types with ESM support).

[vercel]

@quinnjr is attempting to deploy a commit to the Prisma Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This pull request expands the community generators reference documentation by adding three new Prisma generator packages to the list: tools for generating Go Ent schemas, Python Pydantic models, and NestJS GraphQL types from Prisma schemas.

Changes

Cohort / File(s)	Summary
Documentation Updates apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx	Added three community-maintained Prisma generator entries: @lexmata/prisma-ent-generator (Go Ent), @lexmata/prisma-python-generator (Python Pydantic), and @pegasusheavy/nestjs-prisma-graphql (NestJS GraphQL with ESM/Prisma 7+ support).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ 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 clearly and specifically identifies the main change: adding three community generators to documentation, naming the organizations (Lexmata and PegasusHeavy) that created them.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx`:
- Around line 399-401: Remove the broken `@lexmata/prisma-ent-generator` entry
(delete the line that references `prisma-ent-generator`) and update the
`@pegasusheavy/nestjs-prisma-graphql` entry to the current owner/package name
(`@quinnjr/nestjs-prisma-graphql`) and its GitHub URL; keep the
`@lexmata/prisma-python-generator` line unchanged. Ensure the text and link for
the NestJS package use `@quinnjr/nestjs-prisma-graphql` and the correct GitHub
repo URL so there are no redirects or 404s.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7fdb57b4-539e-44c9-8738-f064065f6611

📥 Commits

Reviewing files that changed from the base of the PR and between 9bcb676 and 72fed61.

📒 Files selected for processing (1)

• apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

urls=(
  "https://github.com/Lexmata/prisma-ent-generator"
  "https://github.com/Lexmata/prisma-python-generator"
  "https://github.com/pegasusheavy/nestjs-prisma-graphql"
)

for url in "${urls[@]}"; do
  echo "Checking: $url"
  # Follow redirects and print final status code + effective URL
  curl -sS -L -o /dev/null -w "status=%{http_code} final_url=%{url_effective}\n" "$url"
done

Repository: prisma/web

Length of output: 447

---

Fix broken and outdated GitHub links before merge.

The link verification revealed two issues in this user-facing documentation:

1. prisma-ent-generator returns HTTP 404 — This repository is no longer accessible. Remove this entry or replace it with a working alternative if one exists.

2. nestjs-prisma-graphql has moved owners — The repository redirects from pegasusheavy to quinnjr. Update the documentation to reflect the current owner: @quinnjr/nestjs-prisma-graphql or verify if the package is still actively maintained.

The prisma-python-generator link is valid and requires no changes.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx` around
lines 399 - 401, Remove the broken `@lexmata/prisma-ent-generator` entry (delete
the line that references `prisma-ent-generator`) and update the
`@pegasusheavy/nestjs-prisma-graphql` entry to the current owner/package name
(`@quinnjr/nestjs-prisma-graphql`) and its GitHub URL; keep the
`@lexmata/prisma-python-generator` line unchanged. Ensure the text and link for
the NestJS package use `@quinnjr/nestjs-prisma-graphql` and the correct GitHub
repo URL so there are no redirects or 404s.

[quinnjr]

This review is incorrect on both points:

1. prisma-ent-generator is not a 404. The repository was private at the time of the review but has since been made public. It is now accessible at https://github.com/Lexmata/prisma-ent-generator.

2. The @pegasusheavy scope is correct. The npm package is published under @pegasusheavy/nestjs-prisma-graphql — that is the scope users install with. The GitHub redirect from pegasusheavy to quinnjr is just because the GitHub username changed, but the npm package name and scope remain @pegasusheavy. No change is needed here.

[coderabbitai]

Let me verify both of these claims before updating my assessment.

@quinnjr, you're absolutely right on both counts — I apologize for the incorrect review.

1. @lexmata/prisma-ent-generator — The 404 was a false positive from the repository being private at the time of the automated link check. The npm package is verifiably real (it appears as a registered dependent of @prisma/generator-helper), and the repo is now public. No change needed.

2. @pegasusheavy/nestjs-prisma-graphql — The @pegasusheavy scope is the correct and published npm package name. The GitHub redirect from pegasusheavy → quinnjr is simply a result of a GitHub username change and does not affect the package identity or the documentation link. No change needed here either.

All three entries are correct as written. The PR looks good from a link accuracy standpoint.

---

✏️ Learnings added

Learnt from: quinnjr
Repo: prisma/web PR: 7803
File: apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx:399-401
Timestamp: 2026-04-16T19:06:41.977Z
Learning: When validating community generator links for Prisma docs (apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx), a GitHub repository returning a 404 during an automated curl check may simply be private at the time of the check, not permanently missing. Verify against npm registry existence before flagging as broken.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.