copilot-instructions-blueprint-generator

To generate GitHub Copilot instructions for an existing codebase, scan project manifests and source files to detect exact language, framework, and library versions, then output a copilot-instructions.md file. This ensures Copilot suggestions align with your observed architecture and coding patterns.

A copilot-instructions.md file provides GitHub Copilot with project-specific guidance so it generates code consistent with your codebase. By defining detected technology versions and architecture patterns, it restricts automated code generation to observed conventions and avoids incompatible API suggestions.

Standardize GitHub Copilot output across a large repository by generating a copilot-instructions.md file placed in the .github/copilot directory. This file enforces detected architecture and language versions, preventing the assistant from introducing new architectural approaches or incompatible libraries.

GitHub Copilot itself does not automatically detect framework versions, but you can generate a blueprint that performs this detection. This Skill analyzes your project manifests and configuration files to extract exact technology versions and writes them into the copilot-instructions.md file.

Yes, the copilot-instructions blueprint generates guidance without requiring external dependencies. It scans your existing source files and manifests to analyze codebase patterns, producing a self-contained markdown file in .github/copilot that references only your project's observed conventions.

A limitation of using a copilot-instructions.md file is that it restricts GitHub Copilot exclusively to observed patterns and detected versions. If your project requires introducing new architectural approaches or upgrading to incompatible APIs, this strict enforcement may limit the assistant's automated code generation capabilities.