Generate reversible Drizzle migrations for the Flintmere PostgreSQL schema.
npx skills add https://github.com/Flintmere/flintmere --skill write-migration
Please help me install this Agent Skill. Skill: write-migration Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/write-migration Command: npx skills add https://github.com/Flintmere/flintmere --skill write-migration
Author a Drizzle DB migration for Flintmere. Use when a schema change has been planned and needs a safe, reversible migration committed to the repo. Produces the migration SQL, an up/down round-trip check, and a rollback plan. Operates at Autonomy Level 1 — the user confirms before any migration is generated and never applies it inside this skill.
Describe the planned schema change and request a reversible migration plan.
High-intent search queries and answers about installing and using this skill.
To create a reversible Drizzle migration, describe the planned PostgreSQL schema change and request a migration plan. The skill generates up/down SQL paths, an up/down round-trip check, and rollback documentation without applying the changes.
The safest way to plan an additive schema change is using an autonomy level that requires explicit user confirmation before generating migration files. This ensures the migration plan is complete, self-contained, and ready for staging without applying changes directly.
No, this Drizzle migration generator does not apply changes directly to the database. It strictly separates migration planning from execution, requiring explicit user validation before writing any migration files to the repository for staging.
To document a rollback path for a transforming schema change, generate a reversible migration plan that includes down SQL scripts and rollback documentation. This ensures the database schema change has an auditable, undoable down path.
You need a separate migration file for each schema concern when planning an additive or transforming database change. Scoping one concern per migration ensures strict separation of planning, maintains an audit trail, and keeps the rollback plan self-contained.
A key limitation is that generated Drizzle migrations require explicit user validation before writing files, meaning untested schema modifications cannot be auto-applied. The output is regression-ready for staging and review but requires manual execution downstream.
linenoizeGenerate rollback-aware database migration files and validate schema changes.
cwinvestmentsGenerate database schema migration scripts with rollback strategies.
Prompt-or-Die-LabsGenerate and apply Drizzle Kit migrations for PostgreSQL or SQLite schema changes.
berkcangumusisikGenerate up and down database migration files from schema changes.
