agentleFS
Sign inStart free
melocalexmelocalex/agent-knowledge-demo/skills/migration-review/SKILL.md

migration-review

Skill0 starsChanged 23 days agoApache-2.0View on GitHub

Reviews database schema migrations for safety and reversibility before merge. Use when a PR adds or changes files under a migrations/ directory, or when asked to review a schema change. Not for application-level data fixes.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. jpicklyk/task-orchestrator★ 214same name
    2. paureis/pau-skills★ 2same name
    3. Shri-Phnx/claude-skills★ 2same name
    4. ryukirin/openspec-code-migration★ 0same 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    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:

    If any statement is destructive or the rollback is not a pure inverse, read references/rollback.md and apply its checklist.

    line 17
  2. Very specific:

    Check that money columns are integer minor units (BIGINT ..._minor).

    line 19
  3. Distinctive:

    Write findings as a PR review comment draft for a human to post.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Migration review

  1. List the migration files in the change. Each NNNN_name.sql must have a matching NNNN_name.down.sql. Missing rollback is a blocking finding.
  2. For each statement, classify it as additive (new table, nullable column, new index) or destructive (drop, rename, type change, NOT NULL on an existing column). Destructive changes are blocking unless the PR links a two-step plan.
  3. If any statement is destructive or the rollback is not a pure inverse, read references/rollback.md and apply its checklist.
  4. Check that money columns are integer minor units (BIGINT ..._minor).
  5. Write findings as a PR review comment draft for a human to post. Never run a migration against a shared database. Never approve the PR yourself.

Known mistakes

  • DROP COLUMN in a down migration loses data written after the up ran. Say so explicitly; do not call that rollback "safe".
  • Adding an index on a large table without a concurrent option locks writes.

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