106 published Skills
106 Skills · 7 repositories
Databases
prisma-cli-dev
prisma dev. Reference when using this Prisma feature.
Prisma
@prismaPrisma makes working with databases easy
Prisma makes working with databases easy
United States of America
prisma.io
prisma.io106 published Skills
Curated from public sources. This profile has not been claimed.
GitHub sources106 Skills · 7 repositories
7 sources106 standalone skills106 published skills
Databases
prisma-cli-debug
prisma debug. Reference when using this Prisma feature.
Databases
prisma-cli-db-seed
prisma db seed. Reference when using this Prisma feature.
Databases
prisma-cli-db-push
prisma db push. Reference when using this Prisma feature.
Databases
prisma-cli-db-pull
prisma db pull. Reference when using this Prisma feature.
Databases
prisma-cli-db-execute
prisma db execute. Reference when using this Prisma feature.
Databases
prisma-composer-core-concepts
Use when deploying or managing an app that uses Prisma Composer (`@prisma/composer`): wiring its services and Modules, running it locally, testing composed services, or standing up / tearing down an environment. Triggers on "prisma composer", "@prisma/composer", "prisma app", the `prisma-composer` CLI, `compute()`, `module()`, `contract()`, `service.load()`, `mockService`, `bootstrapService`.
Delivery
upgrade-alchemy-effect
How to upgrade `alchemy` and the `effect` constellation across this repo and keep them consistent for consumers: which packages pin what, why `effect` and every `@effect/*` companion move as one set, what breaks in a typical upgrade, and how to verify a standalone `npm install` still resolves a single `effect`. Use when asked to upgrade or bump alchemy or effect, when a deploy dies inside an alchemy provider with a `TypeError` naming a missing combinator, when `check:npm-effect-resolution` fails, or when deciding whether the alchemy patch is still needed.
Databases
publish-npm-version
Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".
Developer Tools
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.