GitHub Copilot Instructions Parser
Extract and process GitHub Copilot instruction files to understand project conventions, architecture patterns, and development workflows for AI-assisted coding.
What This Skill Does
This skill analyzes GitHub Copilot instruction files (typically found at `.github/copilot-instructions.md`) to extract:
Project architecture and structureKey patterns and conventionsError handling standardsDeveloper workflows (build, run, test, debug)Integration points and external dependenciesFile organization and referencesContribution guidelinesInstructions
When processing a GitHub Copilot instructions file:
1. Identify Core Sections
Parse the document structure and extract:
**Project Overview**: Purpose, architecture, key modules**Patterns & Conventions**: Coding standards, error handling, naming conventions**Developer Workflows**: Build commands, run instructions, test procedures**Integration Points**: External dependencies, APIs, automation hooks**File References**: Key files and their purposes2. Extract Key Information
For each section, identify:
**Commands**: CLI commands, build scripts, test runners**Code Patterns**: Design patterns, architectural conventions**Error Handling**: Exit codes, error message formats, validation logic**Dependencies**: External packages, system requirements, libraries**File Structure**: Module organization, separation of concerns3. Format Output
Present extracted information in a structured format:
Group related guidelines togetherHighlight critical patterns and anti-patternsList all commands with their purposesDocument file relationships and data flowNote any platform-specific requirements4. Validation Rules
Verify all referenced files exist in the contextCheck that exit codes or error enums are definedValidate that workflow commands are completeEnsure external dependencies are documented5. Use Cases
Apply this skill when:
Onboarding to a new project with Copilot instructionsUnderstanding project conventions before making changesReviewing error handling and validation patternsSetting up development environmentContributing to projects with established AI coding guidelinesExample Usage
**Input:** Copilot instructions file for a .NET MSG file parser
**Output:**
Architecture: Modular console app with 7 key filesError Pattern: Centralized `ExitCode` enum with structured messages (`ERROR: <CODE> - <desc>`)Workflows: `dotnet build`, `dotnet run`, `./test_msgparser.sh`Dependencies: MSGReader, libgdiplus (Linux)Data Flow: Program → Arguments → Validator → Parser → ExportImportant Notes
Always respect the error handling conventions specified in the instructionsFollow the documented file structure and don't duplicate validation logic across modulesUse the exact command formats and flags shown in the workflowsCheck for platform-specific dependencies (e.g., Linux packages)Run test scripts before committing changes when specifiedMaintain the documented separation of concerns across modules