SkillsAdd

smithery/cpa03

database-migration-create

Safely creates database migrations

Installation

$ npx skills add smithery/cpa03 --skill database-migration-create
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

azure-storage Same topic
microsoft/azure-skills

Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and D…

567.1K installs
azure-kusto Same topic
microsoft/azure-skills

Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetr…

566.2K installs
supabase-postgres-best-practices Same topic
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-database-setup Same topic
prisma/skills

Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…

269.8K installs
prisma-client-api Same topic
prisma/skills

Prisma Client API reference covering model queries, filters, operators, and client methods. Use…

269.3K installs
prisma-cli Same topic
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs

Also in this package

Other skills from smithery/cpa03.

npx skills add smithery/cpa03
typescript-refactor 0 test-suite-create 0 resilience-check 0 ci-pipeline-update 0

Browse all from smithery/cpa03

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 322 B
  • docs SUMMARY.md 67 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Procedure

  1. Analyze the schema change requirement.
  2. Write the SQL migration file (UP and DOWN if needed).
  3. Review for locking issues or data loss risks.
  4. Update ORM definitions/types.
  5. Apply migration locally to verify.