Skip to content

Migration Instructions Generator

Generates Copilot migration rules by comparing two project versions (branches, commits, tags)

Stars
40,703
Licence
MIT
Files
1 file

What it does

This skill is a template for producing a migration guide. When asked, the agent compares two states of a codebase (for example before and after a framework upgrade) and writes a file called .github/copilot-migration-instructions.md. That file lists old-to-new code patterns, API replacements, and obsolete patterns, so GitHub Copilot can apply the same changes consistently in future edits. The skill is written mainly for GitHub Copilot; it is a prompt and configuration template rather than a tool with its own code.

Great for

  • Teams doing a framework version upgrade who want Copilot to follow the same transformation rules afterwards
  • Engineers planning a large refactor or technology swap who want a written record of the changes
  • Maintainers who want consistent conventions enforced across a codebase during a migration

Skip it if

  • Simple one-off code edits, since the output is a long instruction document that adds overhead (no code is executed to do the work)
  • Projects where the agent cannot read both versions (git history or branches must be available), because the analysis depends on the actual diff
  • Unattended automated rewrites of production code: the generated rules may be wrong, and the skill itself says human validation matters for complex cases

Try asking

  • “Compare the main branch with the v3 branch and generate migration instructions for a framework upgrade”
  • “Analyze the differences between tag v1.4.0 and v2.0.0 and list breaking API changes as a correspondence table”
  • “Create Copilot instructions for moving from one state-management library to another, with examples”
Step-by-step guide: how to use Migration Instructions GeneratorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    generate-custom-instructions-from-codebase.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip generate-custom-instructions-from-codebase.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip generate-custom-instructions-from-codebase.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Set the migration type and scope precisely (for example Framework Version with Specific folder) so the analysis stays focused.
  • Keep automation at Conservative or Balanced first, and require validation, until you have checked that the generated rules are accurate.
  • Review the generated instruction file and test the rules on sample code before relying on them across the repository.

What's inside

  • SKILL.md

Redistributed unmodified from github/awesome-copilot under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.