Review database migration files for naming conventions and dangerous operations. Auto-activates for migration files.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Review the current migration file for naming conventions, rollback presence, and dangerous operations.
Use the current file context to determine which migration file is being worked on. If the user specified a file path, use that. If the context is ambiguous, ask the user which file to review before proceeding.
Extract the file name (not the full path) and check it against two accepted naming formats:
Format A — Timestamp prefix:
Pattern: YYYYMMDDHHMMSS_description.sql
Example: 20260513143207_add_user_roles.sql
.sqlFormat B — Sequential prefix:
Pattern: NNNN_description.sql
Example: 0042_add_user_roles.sql
.sqlIf the file name matches neither format, mark the naming check as FAIL and note the reason.
Read the file content and look for either:
-- rollback, -- down, -- revert, followed by SQL that undoes the migration)-- This migration is irreversible, -- no rollback)If neither is present, mark rollback as NO.
Read the file and scan for these patterns (case-insensitive):
DROP TABLE without IF EXISTS immediately following — flag as WARNINGDROP TABLE IF EXISTS — acceptable, no warningDELETE FROM without a WHERE clause on the same or next line — flag as WARNINGUPDATE without a WHERE clause on the same or next line — flag as WARNINGTRUNCATE on any table — flag as WARNING (destructive, often irreversible in production)DROP COLUMN — flag as NOTICE (may break dependent code; not always dangerous but requires attention)For each match, note the line number.
Present findings in this format:
Migration review: <filename>
Naming convention: PASS
- Format: timestamp-prefix / sequential-prefix
(or)
Naming convention: FAIL
- Reason: <specific reason>
Rollback: YES / NO / MARKED IRREVERSIBLE
- <brief note on what the rollback does, or why it is marked irreversible>
Dangerous operations: NONE
(or)
Dangerous operations:
WARNING line 14: DELETE without WHERE clause
WARNING line 22: TRUNCATE on orders table
NOTICE line 31: DROP COLUMN — confirm no dependent code references this column
Do not modify the migration file. This skill reviews only.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.