Skip to content
TrustedSkillsbeta
Back to all skills

Db Migrate

Official
medusajs·vlatest·database

Automates database schema migrations using MedusaJS's CLI tools, ensuring consistent data structure updates across environments.

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 medusajs/medusa-agent-skills --skill db-migrate -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

medusajs

Matched to the vendor's own GitHub organisation.

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 medusajs/medusa-agent-skills at e9c28cc8ef.

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

Commit
e9c28cc8ef
Manifest
plugins/medusa-dev/skills/db-migrate/SKILL.md
Scanned
1 file, 18 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

What it does

The db-migrate skill enables AI agents to manage and execute database migrations, ensuring that database schemas are updated consistently across different environments. It supports version control of schema changes and provides tools for applying or rolling back migrations.

When to use it

  • When deploying new features that require changes to the database structure.
  • During development to keep local and production databases in sync.
  • When refactoring or improving existing database schemas.
  • To automate repetitive migration tasks across multiple environments.

Key capabilities

  • Execute migration scripts for schema updates.
  • Roll back migrations if issues are detected.
  • Track migration status and history.
  • Support for version-controlled migration files.

Example prompts

  • "Run all pending database migrations."
  • "Rollback the last migration executed on the production database."
  • "Generate a new migration file for adding a users table."

Tips & gotchas

  • Ensure that migration scripts are tested in a development environment before applying them to production.
  • Always back up your database before running destructive or schema-altering migrations.