goose-migrations

Name: goose-migrations
Availability: InStock
Author: hackefeller

Automate Goose SQL migration lifecycle for the Hominem monorepo.

1|Updated Sep 2, 2019

Search Tags:#automation #workflow #database #migrations #schema #sql #goose

Ready to run

npx skills add https://github.com/hackefeller/hominem --skill goose-migrations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: goose-migrations
Source: https://github.com/hackefeller/hominem/tree/main/.codex/skills/goose-migrations
Command: npx skills add https://github.com/hackefeller/hominem --skill goose-migrations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Hominem Goose migrations require careful lifecycle management to avoid drift in database schemas, ensure safe application of changes, and maintain reproducibility across environments.

Core Features & Use Cases

Scaffold new migrations with a standard naming convention
Author, test, and validate Up/Down blocks, then apply via the canonical workflows
Use across the monorepo for repo-specific safety rules and rollout planning

Quick Start

Scaffold a new migration with make db-new-migration NAME=descriptive_change and apply it with make db-migrate-sync

Frequently Asked Questions about goose-migrations

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

FAQPage Schema

How do I create a new SQL database migration in a monorepo?▼

To create a SQL database migration, scaffold a new file using the standard naming convention with make db-new-migration NAME=descriptive_change. This generates a migration file for authoring Up and Down blocks.

What is the safest way to apply SQL schema changes across development environments?▼

Applying SQL schema changes safely requires coordinating the Goose migration lifecycle to avoid schema drift. Use make db-migrate-sync to apply changes and maintain reproducibility across environments.

How does a Goose migration validate database schema types?▼

A Goose migration validates database schema types by running the make db-verify-types workflow. This synchronization step ensures type safety and checks for drift after schema changes.

Can I automate database rollback workflows when testing schema changes?▼

Yes, you can automate database rollback workflows by authoring and validating Down blocks within your migration files. This ensures safe reversal of schema changes during development cycles.

Why do database schemas drift when managing SQL migrations manually?▼

Database schemas drift during manual SQL migrations due to uncoordinated application of changes across environments. Automating the migration lifecycle with standardized workflows prevents this drift and maintains consistency.