li3p/migrate-draft
skills/migrate-draft/SKILL.md
Draft a reversible database migration that follows existing project conventions. Use when adding, changing, renaming, indexing, or removing database schema elements.
data-ai
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add li3p/skills migrate-draftInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 11:10 PM12.8s1 file scanned
SKILL.md
- name:
- migrate-draft
- description:
- Draft a reversible database migration that follows existing project conventions. Use when adding, changing, renaming, indexing, or removing database schema elements.
Migrate Draft
Draft a database migration for: $ARGUMENTS
Workflow
- Identify the migration system:
- Alembic
- Rails
- Prisma
- Drizzle
- Knex
- TypeORM
- raw SQL
- another local convention
- Read representative existing migrations to learn naming, directory layout, up/down style, transaction behavior, and index naming.
- Inspect nearby model, schema, repository, and application code to infer the data shape the migration must support.
- Draft the migration using the local pattern.
Requirements
- Include rollback logic when the migration system supports it.
- Make rollback the inverse of the forward migration.
- For non-null columns, provide a safe default or multi-step backfill plan.
- For destructive changes, call out data loss clearly.
- For indexes and constraints, follow local naming conventions.
- For renames, consider foreign keys, indexes, references, and compatibility with already-deployed application code.
Safety Checklist
Include a checklist covering:
- estimated affected row count
- table lock risk
- backwards compatibility with current app code
- whether deploy and migration can be separated
- what happens if migration fails halfway through
- rollback limits and data loss risks
Create the migration file only when the user asked for implementation. If the user asked for a draft, output the proposed file content and safety notes.
Related Skills
li3p/notion-search
documentation
VerifiedTrustedCommunity
Search Notion for pages or databases by query using marknotion. Use when the user references a Notion page by name rather than URL, when locating a page to publish to or pull from, or when discovering what trackers and docs exist in the connected workspace.
SKILL.mdUpdated May 27, 2026
li3p/notion-pull
documentation
VerifiedTrustedCommunity
Export a Notion page to local Markdown using marknotion. Use when the user wants to pull a spec, design doc, meeting notes, or any Notion page into the repository as a Markdown file, or wants to read Notion content as context for a task.
SKILL.mdUpdated May 27, 2026
li3p/notion-publish
documentation
VerifiedTrustedCommunity
Publish a local Markdown file to a Notion page using marknotion. Use when the user wants to push README, docs, changelogs, or any Markdown content to Notion, either updating an existing page or creating a new one under a parent page.
SKILL.mdUpdated May 27, 2026
li3p/testmatch
testing
VerifiedTrustedCommunity
Generate tests that match an existing project's testing style. Use when adding coverage for a target file, function, bug fix, or edge case while preserving local conventions.
SKILL.mdUpdated Apr 23, 2026