db-migration-governance

Enforce MySQL migration naming, safety, and reversibility rules.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill db-migration-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-migration-governance
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/db-migration-governance
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill db-migration-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The governance skill defines a formal set of rules for MySQL migrations, ensuring consistent naming, safety checks, and reversible changes.

Core Features & Use Cases

  • Enforce migration naming conventions
  • Provide safety and rollback guidelines
  • Offer templates for migration planning and risk assessment

Quick Start

Run a governance check on your migrations to ensure naming, safety, and reversibility.

Frequently Asked Questions about db-migration-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce safe MySQL migrations in a Laravel CI pipeline?

Migration naming conventions standardize file and class names to ensure chronological ordering and team clarity. This skill enforces consistent naming across MySQL migrations, making it easier to track schema changes and identify migration purposes during code reviews.

What is the best way to ensure database migration reversibility without raw SQL?

Migration naming conventions standardize file and class names to ensure chronological ordering and team clarity. This skill enforces consistent naming across MySQL migrations, making it easier to track schema changes and identify migration purposes during code reviews.

Does this database migration governance skill work with existing Laravel workflows?

Migration naming conventions standardize file and class names to ensure chronological ordering and team clarity. This skill enforces consistent naming across MySQL migrations, making it easier to track schema changes and identify migration purposes during code reviews.

Why do I need idempotent checks and atomic changes for MySQL schema updates?

Migration naming conventions standardize file and class names to ensure chronological ordering and team clarity. This skill enforces consistent naming across MySQL migrations, making it easier to track schema changes and identify migration purposes during code reviews.

When should I not use forward-only database migrations?

Migration naming conventions standardize file and class names to ensure chronological ordering and team clarity. This skill enforces consistent naming across MySQL migrations, making it easier to track schema changes and identify migration purposes during code reviews.