Ship the prisma-platform-core-concepts skill in the prisma package - #245
Ship the prisma-platform-core-concepts skill in the prisma package#245tylerhogarth wants to merge 2 commits into
Conversation
The prisma package now carries an agent skill covering the platform: the workspace/project/branch model, preview environments, the two deploy paths, services and versions, the Compute runtime, Prisma Postgres, object storage, environment variables, and the local development stack. Packaging follows the composer pattern: the tracked source lives in skills/, stage-skills.mjs stages it into the tarball at prepack, set-version.ts stamps metadata.library_version on every bump, and check-skill-packaging.mjs (wired into pr-quality) packs the package and verifies the stamp and byte equality against the source. The prisma package joins the skills-sync allowlist so consumers receive the skill via prisma skills sync. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
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 (11)
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. Important Approval pendingCodeRabbit has no unresolved comments, but it could not review the latest commit because the review limit was reached. Follow the review guidance in this comment to continue. Summary by CodeRabbit
WalkthroughThe PR adds the Merge Risk: ⚪ Minimal · up to This change adds and packages a Prisma Platform concepts skill without any identified merge-blocking correctness, security, availability, or deployment risk; it is ready to merge after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 5 files. (6 skipped: 6 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Review ruling on #245: the CLI is self-documenting and a command table risks giving the agent context that conflicts with the shipped surface. The skill routes to --help instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
The
prismapackage now ships an agent skill defining the Prisma Platform's core concepts, the same way@prisma/composerand the ORM anchor packages ship theirs. Consumers receive it throughprisma skills sync.Changes
skills/prisma-platform-core-concepts/SKILL.mdcovers structures, hierarchies, relationships, and workflows: the workspace/project/branch model, branches as preview environments, the two deploy paths (GitHub app recommended, CLIdeploy --stage), services and versions, the Compute sleep model, Prisma Postgres, object storage, the env-var class/scope model, and the local development stack. It is deliberately not a CLI reference; it routes command surfaces to--help.skills/README.mdrecords the authoring rules.scripts/stage-skills.mjsstages skills into the package atprepack, selected by each skill'smetadata.libraryfrontmatter.packages/prismaaddsskillstofiles; the staged copy is gitignored.scripts/set-version.tsnow stampsmetadata.library_versionin every skill on a lockstep bump, via the newscripts/skill-frontmatter.tshelpers.scripts/check-skill-packaging.mjs(root scriptcheck:skill-packaging, newpr-qualityjob) packs the package the way publish does and checks the tarball carries the skill, stamped with the packed version and byte-identical to the tracked source.prismajoinsSKILL_SOURCE_PACKAGESinpackages/cli/src/lib/skills/allowlist.ts, the deliberate per-package trust decision that lets sync install from it.Why
Staging is frontmatter-driven rather than a hardcoded table so the skill list has one source of truth, and it runs at
prepackrather than build so a stale turbo cache can never produce a tarball without it. The tarball check exists because none of the failure modes (missingfilesentry, failed staging, hand-edited stamp) show up in unit tests; they show up in what npm uploads. The pattern is a direct port of the one proven in prisma/composer.🤖 Generated with Claude Code