feat: sync agent skills through Prisma CLI - #61
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (9)
Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. Summary by CodeRabbit
WalkthroughThe dependency map removes Merge Risk: ⚪ Minimal · up to The PR updates generated-project dependency and skill synchronization behavior with stated checks and scaffold validations passing; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
PR preview published
|
Summary
prisma@nextin generated Node projects and use its localprismabinary for ORM and Composer scriptsprisma.config.ts, then runprisma initafter dependency installation so the CLI syncs skills from installed Prisma packagesnuxt preparestep before syncingThis keeps the old ORM skills installer disabled (
--skip-skills/--no-skill), so generated projects no longer source skills fromprisma/skills. Deno remains on its existing ORM-only path until the consolidated CLI can start under Deno.Verification
bun run checkbun run typecheckbun run test:unitbun run test:e2eprisma-composerskill and chained postinstall