generate-custom-instructions-from-codebase

Generate GitHub Copilot migration instructions by analyzing code evolution between project references.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill generate-custom-instructions-from-codebase-gabeujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-custom-instructions-from-codebase
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/generate-custom-instructions-from-codebase
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill generate-custom-instructions-from-codebase-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of precise instructions for GitHub Copilot, enabling it to understand and replicate code migration and evolution patterns across different project versions.

Core Features & Use Cases

  • Code Evolution Analysis: Compares project states to identify structural and code transformation patterns.
  • Copilot Instruction Generation: Creates detailed .github/copilot-migration-instructions.md files.
  • Use Case: Migrating a large codebase from an older framework version to a newer one. This Skill analyzes the differences, generates rules for Copilot to automatically refactor code, and ensures consistency during the transition.

Quick Start

Generate migration instructions for GitHub Copilot by analyzing the code evolution between the 'main' and 'develop' branches.

Frequently Asked Questions about generate-custom-instructions-from-codebase

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

FAQPage Schema
How do I generate GitHub Copilot instructions for code migration from an existing codebase?

To generate GitHub Copilot instructions for code migration, analyze the code evolution between project references to identify structural changes and new patterns. This process produces a detailed `.github/copilot-migration-instructions.md` file to guide automated refactoring.

What is code evolution analysis and when do I need it for framework upgrades?

Code evolution analysis compares project states to identify structural and code transformation patterns. You need it during technology migrations or framework upgrades to extract rules that maintain consistency and guide automated refactoring across the codebase.

Can I customize the scope and automation level for code migration instructions generation?

Yes, you can configure the analysis scope, automation levels, and validation requirements to tailor migration strategies. This customization ensures the generated GitHub Copilot instructions align with specific project needs during architecture refactoring.

What's the best way to automate refactoring when migrating a large codebase to a newer framework version?

The best way to automate refactoring is analyzing code differences between project versions to generate precise rules for GitHub Copilot. This ensures consistency during the transition by replicating established code migration patterns automatically.

Do I need specific project branches to generate accurate code migration instructions?

Yes, you need project references like distinct branches to compare code evolution. Analyzing the differences between these specified project states allows the tool to identify structural changes and generate accurate migration instructions.

Why use generated instructions instead of manual refactoring for technology migrations?

Using generated instructions for technology migrations automates the creation of precise rules for GitHub Copilot, avoiding manual inconsistencies. It identifies new patterns from code evolution to ensure consistent automated refactoring across the entire codebase.