feat: add prisma-mongodb-upgrade skill#20
Merged
Conversation
MongoDB projects are the one Prisma cohort with no path to Prisma 7 (v6 is the terminal classic-ORM major for MongoDB; v7 ships no connector). Agents routinely mis-advise these projects: recommending an impossible v7 upgrade or silently rewriting apps onto SQL. This skill frames the real decision — stay on the latest v6 deliberately (the default for production today) or migrate to Prisma Next — and carries the migration mechanics: schema-to-contract mapping, client API mapping including the raw lanes and the transactions gap, migrations story, and a no-data-moves cutover checklist. Prisma Next claims are verified against prisma/prisma-next at commit a2791c5dd59d579b4b3052942ae7f8fe5e2ee852; v6 claims cite released v6 documentation. Cross-links added: prisma-upgrade-v7 and prisma-database-setup now route MongoDB version questions to this skill, and the README gains the skill entry. Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>
tensordreams
added a commit
to prisma/prisma
that referenced
this pull request
Jul 6, 2026
The mongodb-upgrade-skill slice (adopted work TML-2973) closed the gap the operator surfaced: probe verdict recorded (Next MongoDB = present but partial, POC status), skill authored stay-on-v6-first with cited migrate-now branch, PR open on prisma/skills. Scoreboard 9 PASS, findings log still empty.
aqrln
marked this pull request as draft
July 6, 2026 12:38
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
aqrln
reviewed
Jul 6, 2026
Correct the maturity framing per review: MongoDB support in Prisma Next is Early Access with GA planned after Postgres, and migrating is the encouraged path for MongoDB users; staying on v6 remains a legitimate choice where hard blockers apply, stated without discouraging framing. Blocker questions become agent self-checks (grep for $transaction instead of asking the user). Transactions guidance now states affirmatively that the underlying mongodb driver is directly available for sessions today, with the facade wrapper expected soon. Internal prisma-next source paths removed from user-facing prose in favor of Prisma Next's own skills. Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>
aqrln
reviewed
Jul 6, 2026
Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>
aqrln
marked this pull request as ready for review
July 6, 2026 15:42
ankur-arch
reviewed
Jul 8, 2026
Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>
Member
|
@AmanVarshney01 please take another look |
AmanVarshney01
approved these changes
Jul 9, 2026
AmanVarshney01
left a comment
AmanVarshney01
left a comment
Member
There was a problem hiding this comment.
Time to merge is now 🎉
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this skill exists
MongoDB projects are the one Prisma cohort with no road into Prisma 7: v6 is the terminal classic-ORM major for MongoDB, and v7 never ships a MongoDB connector. Agents encountering these projects routinely mis-advise them — recommending an impossible "upgrade to Prisma 7" (the
prisma-upgrade-v7guide reads as generally applicable) or, worse, silently rewriting the app onto a SQL database. This skill gives agents the real decision to relay: stay on the latest v6 deliberately, or migrate to Prisma Next.Structure: stay-on-v6 lead, with a real migrate-now branch
The skill leads with stay-on-v6 as the production default, because Prisma Next's own roadmap classifies its MongoDB target as a POC ("validating that non-SQL targets work within the framework") and excludes it from the current Early Access and GA target sets (prisma-next
ROADMAP.md), the package line is pre-1.0 with breaking changes between minors, and the Next Mongo façade does not yet exposedb.transaction(...).The migrate-now branch is nonetheless real and mechanically detailed — Next's MongoDB implementation is deep (full ORM + pipeline builder + raw lane + first-class plan/migrate/verify/sign migrations, tested against real in-memory MongoDB) — with explicit no-go signals (façade transactions required; pre-1.0 upgrade aversion) and a no-data-moves cutover checklist.
Contents:
SKILL.mdrouter + 5 references (decision framing, schema/contract mapping, client API mapping, migrations mapping, cutover verification). Cross-links: a MongoDB routing block inprisma-upgrade-v7, a routing note inprisma-database-setup, and a README entry.Every behavioral claim carries a citation: Prisma Next claims are pinned to prisma/prisma-next @
a2791c5dd59d579b4b3052942ae7f8fe5e2ee852(stated in the skill, with a verify-before-acting note since Next is Early Access); v6 claims cite the released v6 docs (URLs with anchors verified at authoring time).Open question for maintainers:
metadata.versionsemanticsExisting ORM skills carry the targeted ORM version (e.g.
prisma-upgrade-v7is"7.6.0"), but this skill spans v6 → Prisma Next and targets no single ORM version. Working position: the skill is versioned as itself, starting at"0.1.0", with the verified prisma-next commit named in the body. Happy to adopt whatever convention you prefer.Validation
Branch-ref install into a scratch dir: