Does this skill support reversible migrations?

Yes, the skill automatically generates both .up.sql and .down.sql files to ensure every schema change can be fully rolled back.

Does it enforce documentation within the database?

Yes, one of the primary rules is that every field and every table must include a COMMENT to maintain schema clarity.

Can I use this for adding indexes to existing tables?

Absolutely. The skill includes specific patterns for adding and dropping both standard indexes and unique keys.

Which database engines are supported?

While the syntax is standard SQL, the skill specifically targets MySQL/MariaDB using the InnoDB engine and utf8mb4 character set as per Go project best practices.

How does it handle file naming for migrations?

It uses a 14-digit timestamp (yyyymmddhhiiss) followed by a 3-digit sequence number and a snake_case description to ensure correct execution order.

Go Database Migration Manager

Name: Go Database Migration Manager
Author: LukeLogix

byLukeLogix

데이터베이스 관리

Generates standardized golang-migrate SQL files with timestamp-based naming and strict schema conventions.

소개

This skill automates the creation of database migration pairs (up.sql and down.sql) specifically designed for Go projects using the golang-migrate library. It ensures consistent naming conventions using precise timestamps, enforces best practices like mandatory field comments and InnoDB engine usage, and provides standardized templates for creating tables, modifying columns, and managing indexes to maintain a robust, documented, and reversible database schema.

주요 기능

Standardized field type mappings for Go-to-MySQL compatibility
0 GitHub stars
Synchronized generation of up.sql and down.sql for full rollbacks
Pre-configured templates for table creation, column shifts, and index management
Automatic timestamp-based naming with 3-digit sequence numbering
Enforced SQL standards including utf8mb4 and InnoDB engine defaults

사용 사례

Initializing new database tables with standardized audit fields like created_at and updated_at
Modifying existing schema structures while ensuring a matching rollback script exists
Implementing database indexes and unique constraints following strict naming conventions

소개

주요 기능

Standardized field type mappings for Go-to-MySQL compatibility
0 GitHub stars
Synchronized generation of up.sql and down.sql for full rollbacks
Pre-configured templates for table creation, column shifts, and index management
Automatic timestamp-based naming with 3-digit sequence numbering
Enforced SQL standards including utf8mb4 and InnoDB engine defaults

사용 사례

Initializing new database tables with standardized audit fields like created_at and updated_at
Modifying existing schema structures while ensuring a matching rollback script exists
Implementing database indexes and unique constraints following strict naming conventions