Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.
This skill generates migration and code-evolution instructions for GitHub Copilot by analyzing the differences between two versions of a project — two branches, commits, or tags. It solves the problem of maintaining consistency during technology migrations, major refactoring, or framework upgrades: once the transformation patterns between a before and after state are captured, Copilot can automatically apply the same changes during future work rather than relying on developers to remember each rule.
The skill is driven by configuration variables (migration type, source and target references, analysis scope, change focus, automation level, whether to generate examples, and whether validation is required). It defines a multi-phase methodology: a comparative state analysis that detects structural changes, dependency changes, and code transformations tailored to the migration type (framework version, architecture refactoring, technology migration); extraction of repetitive transformation patterns into before/after correspondence rules; and generation of a `.github/copilot-migration-instructions.md` file. That output documents mandatory transformations, transformations requiring validation, API correspondence tables, new patterns to adopt, obsolete patterns to avoid, file-type-specific guidance, validation and security control points, manual-escalation cases, and monitoring metrics. Optional phases add contextual before/after code examples and iterative rule optimization.
It targets developers, architects, and teams undertaking systematic migrations who want Copilot to reproduce their evolution decisions consistently. Use cases include upgrading a framework version, refactoring architecture, or replacing one technology with another while keeping conventions coherent and avoiding deprecated patterns. The skill reads version-control history and project files and produces an instruction document; it performs git comparisons and file analysis but no destructive operations or credential handling, so it rates as low risk.
A .github/copilot-migration-instructions.md file containing automatic transformation rules, API correspondence tables, patterns to adopt and avoid, validation control points, and monitoring metrics that guide Copilot during future changes.
Configuration variables including the migration type, a source and target reference (branch, commit, or tag), the analysis scope, the change focus, an automation level, and flags for generating examples and requiring validation.
Framework version upgrades, architecture refactoring, technology migrations, dependency updates, and pattern changes — with the analysis tailored to the selected migration type.
Yes. A Conservative level omits mandatory automatic-transformation rules, while Balanced and Aggressive include them; Aggressive also adds iterative optimization to maximize automation and reduce false positives.
It compares the two project states — folder structure, dependencies, and code — extracts repetitive transformations, and builds a before/after correspondence matrix, including breaking changes and obsolete patterns.
Quick Setup:
.claude/skills/Repository
github/awesome-copilot