agentsclimarketplace

Sql migration reviewer

Skill aneesh-a7/skill-lint/examples/good/sql-migration-reviewer

ruff for SKILL.md: catch bad triggers, token bloat, and structural mistakes before you publish a skill.

Install
npx -y skills add aneesh-a7/skill-lint --skill sql-migration-reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Reviews a SQL migration file for safety before it ships to production, checking for locking risk, missing rollback statements, unsafe column drops, and index changes made without CONCURRENTLY. Use when the user asks to review, check, or sanity-test a migration file, a schema change, or a raw `.sql` file that alters a table. Not for writing migrations from scratch, and not for reviewing application-level ORM code that contains no raw SQL.

SKILL.md

1.4 KB, 215 tokens by cl100k_base, as published. Nobody here has run it

SQL Migration Reviewer

Reads a single .sql migration file and flags changes that are risky to run against a live database: missing CONCURRENTLY on index creation, DROP COLUMN without a prior deprecation window, unbounded UPDATE/DELETE, and migrations with no corresponding rollback.

Usage

Point it at a migration file and ask for a review:

review this migration for safety: migrations/0042_add_user_status.sql

The output is a list of findings, each tied to the specific statement that triggered it, with a suggested rewrite.

See references/checklist.md for the full set of checks and the reasoning behind each one.

When NOT to use

  • Writing a new migration from scratch (this only reviews existing SQL).
  • Reviewing ORM migration code with no raw SQL statements to inspect.
  • Reviewing schema changes for a database engine other than Postgres/MySQL, where the locking semantics below don't apply.

What ships with it: 1 file

958 B alongside SKILL.md

references/

Keep looking

Skills are one crate of 327,132. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.