agentleFS
Sign inStart free
ByronScottJonesByronScottJones/Agents/skills/execute-database-migration/SKILL.md

execute-database-migration

Skill7 starsChanged 2 months agoMITView on GitHub

Use when planning, validating, testing, executing, or rolling back a database schema migration. Defaults to read-only validation and dry-run behavior; production mutation requires explicit confirmation and a recovery plan.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test against representative sanitized data where possible.

    line 28
  2. Distinctive:

    Never ask for or print database credentials.

    line 36
  3. Distinctive:

    Never execute against production without explicit confirmation.

    line 37
  4. Distinctive:

    Do not claim rollback support unless it has been verified.

    line 38

≈ “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

Execute Database Migration

Implement database.md and disaster-recovery.md as a safe migration workflow.

Parameters

  • database: target identifier; never require a secret in chat.
  • migrationsPath: default db/migrations/.
  • currentVersion, targetVersion: detected unless supplied.
  • mode: validate, plan, test, execute, or rollback; default validate.
  • dryRun: default true.
  • backupRequired: default true for execute and rollback.
  • checkBackwardCompatibility: default true.
  • timeout: default 30m.
  • format: summary or json; default summary.

Workflow

  1. Detect the migration framework and current schema version.
  2. Validate syntax, ordering, checksums, permissions, and dependencies.
  3. Analyze expand/migrate/contract compatibility with old and new application versions.
  4. Test against representative sanitized data where possible.
  5. For execute, require confirmation, verify backup/recovery readiness, apply the reviewed migration, and run schema and application smoke checks.
  6. For rollback, prefer a tested down migration or restore procedure; report when rollback is impossible or destructive.

Safety

  • Never ask for or print database credentials.
  • Never execute against production without explicit confirmation.
  • Do not claim rollback support unless it has been verified.
  • Capture timing, locks, affected rows, and validation results without sensitive data.

Output

Return current and target versions, schema changes, compatibility findings, backup status, execution status, smoke checks, rollback limits, and next steps.

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