Best use case
migrate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Plan and execute migrations (database, API, framework)
Teams using migrate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/migrate/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/migrate/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/migrate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How migrate Compares
| Feature / Agent | migrate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Plan and execute migrations (database, API, framework)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Plan and execute migration for: $ARGUMENTS Steps: 1. Assess the scope and impact of the migration 2. Create a step-by-step migration plan with rollback strategy 3. Write migration scripts or code changes 4. Test the migration including rollback path 5. Document breaking changes and migration guide
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.