GitHub Copilot¶

GitHub Copilot uses a unique .instructions.md file extension for its instruction files and supports MCP server configuration through VS Code's MCP integration with a 128-tool limit.

Overview¶

Instructions¶

GitHub Copilot reads instruction files from .github/instructions/ in the project root. Files must use the .instructions.md extension -- plain .md files are ignored.

DevSync installs one file per instruction with the correct extension:

my-project/
  .github/
    instructions/
      code-style.instructions.md
      testing-standards.instructions.md

Installing Instructions¶

# Install a package from a local path
devsync install ./my-package --tool copilot

# Install a package from a Git repository
devsync install https://github.com/acme/standards --tool copilot

Alternative: copilot-instructions.md¶

GitHub Copilot also supports a single .github/copilot-instructions.md file for project-wide instructions. DevSync uses the multi-file .github/instructions/ approach instead, which provides better organization and granular control.

Instruction File Format¶

Copilot instruction files are plain markdown:

# TypeScript Conventions

- Use strict TypeScript configuration
- Prefer interfaces over type aliases for object shapes
- Use branded types for domain identifiers

Copilot supports glob-based file matching via VS Code settings, allowing instructions to apply conditionally based on the file being edited.

MCP Server Configuration¶

GitHub Copilot supports MCP servers through VS Code's built-in MCP integration with a limit of 128 tools.

Configuration Locations¶

{
  "servers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "DATABASE_URL": "postgresql://localhost:5432/mydb"
      }
    }
  }
}

{
  "servers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects"]
    }
  }
}

Installing MCP via Packages¶

devsync install ./my-package --tool copilot

DevSync merges MCP entries into .vscode/mcp.json.

Unsupported Components¶

GitHub Copilot does not support hooks, commands, skills, workflows, or resources through DevSync. Unsupported components are skipped during package installation.

Detection¶

DevSync detects GitHub Copilot by checking for the VS Code configuration directory and the Copilot extension. Verify with:

devsync tools

Package Component Support¶

Example: Project Setup¶

# Install team standards from a Git repository
devsync install https://github.com/acme/standards --tool copilot

Result:

my-project/
  .github/
    instructions/
      code-style.instructions.md
      testing.instructions.md
  .vscode/
    mcp.json                              # If package includes MCP servers