create-migration

Generate versioned JavaScript migration files for JSON configuration updates.

22|4|Updated Apr 14, 2025
One-click install
npx skills add https://github.com/intrafind/ihub-apps --skill create-migration-intrafind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-migration
Source: https://github.com/intrafind/ihub-apps/tree/main/.claude/skills/create-migration
Command: npx skills add https://github.com/intrafind/ihub-apps --skill create-migration-intrafind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of versioned configuration migration files, ensuring consistency and adherence to project standards when modifying application configurations.

Core Features & Use Cases

  • Versioned Migrations: Generates new migration files with sequential version numbers.
  • Structured Format: Follows a Flyway-style pattern for easy management and execution.
  • Use Case: When adding a new default setting to providers.json, use this Skill to create a migration file that safely introduces this change without overwriting existing configurations.

Quick Start

Create a new migration file for adding a default value to a configuration setting.

Frequently Asked Questions about create-migration

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

FAQPage Schema
How do I create versioned configuration migration files in JavaScript?

You can generate versioned JavaScript migration files for server-side configuration updates that add default values, rename keys, or restructure JSON configurations using a Flyway-style pattern for consistent management.

When do I need a migration file for updating JSON configurations?

You need a configuration migration file when adding new default settings to JSON files like providers.json, ensuring changes are introduced safely without overwriting existing configurations during updates.

Do I need Node.js to run server-side config migrations?

Yes, generating and executing these JavaScript migration files requires a Node.js environment, as the process depends on Node.js for execution and performing file system operations.

What's the best way to manage sequential version numbers for config migrations?

This approach automatically generates new migration files with sequential version numbers following a Flyway-style pattern, ensuring structured and traceable configuration changes across project updates.

Can I restructure JSON configurations and rename keys with a migration?

Yes, the generated JavaScript migration files support restructuring JSON configurations and renaming keys, allowing you to safely modify server-side configuration formats while maintaining version history.