agentleFS
Sign inStart free
arslanvuzmalarslanvuzmal/VoxCircuit/.agents/skills/database-migration-safety/SKILL.md

database-migration-safety

Skill2 starsChanged 3 months agoMITView on GitHub

Ensures PostgreSQL schema migrations are non-destructive, preserve multi-tenant workspace isolation, and execute safely in development and production environments.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. cvsz/zomega★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use before modifying prisma/schema.prisma or running database migration commands (prisma migrate dev, prisma migrate deploy).

    line 10
  2. Distinctive:

    Verify non-destructive field modifications (prefer adding optional fields or controlled defaults over dropping columns).

    line 22
  3. Very specific:

    Run npx prisma validate to confirm schema integrity.

    line 23
  4. Distinctive:

    Verify foreign key constraints and cascade rules.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Database Migration Safety Skill

When to Use

Use before modifying prisma/schema.prisma or running database migration commands (prisma migrate dev, prisma migrate deploy).

Inputs Required

  • Proposed schema changes.
  • Current database state.
  • Target environment (Local PostgreSQL / Production Supabase).

Step-by-Step Process

  1. Inspect proposed model or field alterations in prisma/schema.prisma.
  2. Confirm every business data model retains mandatory workspaceId foreign key and index.
  3. Verify non-destructive field modifications (prefer adding optional fields or controlled defaults over dropping columns).
  4. Run npx prisma validate to confirm schema integrity.
  5. Apply migration in local development environment.
  6. Verify foreign key constraints and cascade rules.

Decision Tree

  • Does schema change drop existing tables/columns?
    • YES -> Require explicit audit & non-destructive migration path.
    • NO -> Validate schema -> Generate migration file -> Test migration rollforward.

Validation Checklist

  • Every model includes id, createdAt, updatedAt, and workspaceId (where tenant-scoped).
  • Composite indexes created for high-frequency queries (e.g., [workspaceId, status]).
  • Production deployments use prisma migrate deploy without destructive reset.

Failure Conditions

  • Dropping production tables or removing workspace isolation constraints.

Expected Output

Verified migration plan and updated Prisma schema with index validation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free