GitHub Copilot Instructions Converter

This skill converts GitHub Copilot instructions files (`.github/copilot-instructions.md` or similar) into comprehensive project context documentation that helps AI coding assistants understand the codebase structure, technologies, conventions, and development workflows.

What This Skill Does

When given a GitHub Copilot instructions file, this skill:

1. Analyzes the repository purpose and key features

2. Extracts technology stack and architectural patterns

3. Identifies important files, directories, and their purposes

4. Documents workflows, build processes, and development practices

5. Captures domain-specific context and conventions

6. Formats everything into clear, structured documentation

Instructions

When converting a GitHub Copilot instructions file:

1. **Identify Repository Context**

- Extract the repository purpose and primary goals

- Identify the main problem being solved or use case being addressed

- Note any specific domain knowledge required (e.g., game servers, APIs, data processing)

2. **Document Technology Stack**

- List all technologies, frameworks, and tools mentioned

- Note specific versions if provided

- Identify build systems, package managers, and deployment tools

- Document CI/CD systems and automation workflows

3. **Map Project Structure**

- Document key directories and their purposes

- Identify configuration files and their locations

- Note important scripts and their functionality

- Map relationships between different parts of the codebase

4. **Extract Development Workflows**

- Document build processes and commands

- Identify testing and validation procedures

- Note deployment and release processes

- Capture any automated workflows (GitHub Actions, etc.)

5. **Capture Best Practices and Conventions**

- Document coding standards and patterns

- Note architectural decisions and rationale

- Identify security considerations

- Capture contribution guidelines and scope

6. **Format Output**

- Use clear section headers

- Include code examples where relevant

- Create tables for structured data (supported options, versions, etc.)

- Add notes and caveats where important

- Keep language concise but comprehensive

7. **Preserve Context for AI**

- Include "helpful context" sections that guide AI assistants

- Document volume mappings, environment variables, and runtime configurations

- Note common debugging scenarios and solutions

- Provide suggestions for AI assistance tasks

Output Format

Structure the converted documentation with:

Examples

**Input**: Copilot instructions for a Dockerized game server project

**Output**: Comprehensive documentation covering Docker setup, supported games, configuration files, volume mappings, CI/CD workflows, and specific guidance for assisting with Dockerfiles, shell scripts, and GitHub Actions.

**Input**: Copilot instructions for a web application

**Output**: Documentation of framework versions, API routes, database schema, authentication flow, deployment pipeline, and guidance for assisting with component development, API endpoints, and database migrations.

Important Notes