generate-custom-instructions-from-codebase

Generates GitHub Copilot migration instructions by analyzing code differences between two project versions.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill generate-custom-instructions-from-codebase-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-custom-instructions-from-codebase
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/generate-custom-instructions-from-codebase
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill generate-custom-instructions-from-codebase-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When migrating frameworks, refactoring architecture, or upgrading dependencies, teams lose the knowledge of how transformations were applied, making future changes inconsistent. This Skill analyzes the differences between two project states (branches, commits, or tags) and produces a reusable Copilot instructions file that encodes the transformation rules. ## Core Features & Use Cases - Comparative State Analysis: Detects structural changes, moved files, dependency updates, and API differences between a source and target reference. - Transformation Rule Generation: Produces a .github/copilot-migration-instructions.md file with mandatory transformations, API correspondence tables, obsolete patterns, and before/after code examples. - Configurable Scope: Supports migration types (framework version, architecture refactoring, technology migration, dependency updates), automation levels (conservative, balanced, aggressive), and optional validation checkpoints. - Use Case: After upgrading a project from Angular 14 to Angular 17, run this Skill against the two release tags to generate instructions so Copilot automatically applies the same patterns to all future code changes. ## Quick Start Ask the AI to analyze the differences between the main branch and the v2.0 release tag and generate Copilot migration instructions for the framework upgrade.

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 a framework migration?

Provide a source reference (branch, commit, or tag) and a target reference representing the before and after states. The Skill compares the two versions, extracts transformation patterns, and writes a copilot-migration-instructions.md file with rules Copilot applies to future code.

What migration types does this instruction generator support?

It supports framework version upgrades, architecture refactoring, technology migration, dependency updates, and pattern changes. Each type triggers a tailored analysis, such as API change detection for framework upgrades or abstraction mapping for refactoring.

Can I compare two git branches or commits to extract migration patterns?

Yes. The Skill accepts branches, commits, or tags as source and target references, then analyzes structural changes, moved files, dependency differences, and code transformations between those two states.

Does the generated instructions file include before and after code examples?

Yes, when the GENERATE_EXAMPLES variable is set to true. Each detected pattern gets a before/after code sample plus explicit Copilot instructions describing the trigger and transformation steps.

When should I use conservative versus aggressive automation levels?

Use conservative when transformations carry business risk and need human review, since it limits automatic rules. Use aggressive for well-tested mechanical migrations where maximizing automation and minimizing manual validation is acceptable.