Skip to content
TrustedSkillsbeta
Back to all skills

Prisma Migration Assistant

Checked
patricio0312rev·vlatest·database·MIT

Helps with Prisma ORM, migration as part of working with databases and data persistence workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add patricio0312rev/skills --skill prisma-migration-assistant -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

patricio0312rev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned patricio0312rev/skills at 79ea6af485.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79ea6af485
Manifest
db-management/prisma-migration-assistant/SKILL.md
Scanned
1 file, 348 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The Prisma Migration Assistant streamlines database evolution by generating, reviewing, and applying schema migrations directly within your development workflow. It acts as an intelligent pair programmer for database changes, ensuring type safety and consistency across your Prisma models.

When to use it

  • Automating the creation of migration files when updating Prisma schema definitions.
  • Resolving complex conflicts or errors during the migration execution process.
  • Validating proposed schema changes against existing database constraints before deployment.
  • Integrating into CI/CD pipelines to ensure consistent database updates across environments.

Key capabilities

  • Generates Prisma migration files from schema modifications.
  • Analyzes and suggests fixes for failed or incomplete migrations.
  • Provides context-aware assistance for database refactoring tasks.
  • Supports the full lifecycle of database version control with Prisma.

Example prompts

  • "Create a new migration to add a status field to the User model with a default value of 'active'."
  • "Review this proposed schema change and explain any potential conflicts it might cause in the current database state."
  • "Generate a migration script to rename the email column to user_email across all related tables."

Tips & gotchas

Ensure your Prisma client is up to date before running generated migrations to avoid compatibility issues. Always review the generated SQL statements carefully, especially when altering data types or removing columns, as these actions can be irreversible without backups.