AI Dev Tools Sync
Synchronize Claude Code and GitHub Copilot configurations to maintain feature parity.
Summary
Goal: Synchronize Claude Code and GitHub Copilot configurations to maintain feature parity across both AI development tools.
| Step | Action | Key Notes |
|---|
| 1 | Identify change scope | Skills, prompts, agents, instructions, or workflows |
| 2 | Map equivalents | Claude SKILL.md <-> Copilot prompt.md, etc. |
| 3 | Apply changes | Update both platforms' config files |
| 4 | Verify parity | Ensure both tools have matching capabilities |
Key Principles:
- Claude skills live in , Copilot prompts in
- Copilot auto-reads Claude skills — avoid duplication where possible
- Agents are shared in for both platforms
When to Use
Activate this skill when:
- User asks to update Claude Code or Copilot setup
- User wants to add/modify skills, prompts, agents, or instructions
- User wants both tools to work similarly
- User asks about AI dev tool configuration
Quick Reference
| Claude Code | GitHub Copilot | Location |
|---|
| SKILL.md | SKILL.md | + |
| skills/*/SKILL.md | prompts/*.prompt.md | + |
| agents/*.md | agents/*.md | (shared) |
| workflows/*.md | - | |
| CLAUDE.md | copilot-instructions.md | Root + |
| - | instructions/*.md | (applyTo patterns) |
| - | chatmodes/*.chatmode.md | |
GitHub Copilot Features Catalog
Complete catalog of GitHub Copilot customization features (as of 2026).
Configuration Files
Repository-Level ()
| File/Folder | Purpose | Format |
|---|
| Global instructions for all Copilot interactions | Markdown |
instructions/*.instructions.md
| Path-scoped instructions with frontmatter | Markdown + YAML |
| Reusable prompts (slash commands) | Markdown + YAML |
| Agent definitions | Markdown + YAML |
| Agent skills with bundled resources | Markdown + YAML |
| Custom chat personalities | Markdown + YAML |
| Master agent routing file | Markdown |
Also Supported (Backward Compatibility)
- - Copilot auto-reads Claude skills
- - Copilot reads if present
- - Gemini CLI format
Feature Details
Custom Instructions ()
Root instructions auto-included in every request.
markdown
# Project Guidelines
- Use TypeScript for all new files
- Follow BEM naming for CSS classes
Path-Scoped Instructions ()
Apply to specific file patterns via
:
yaml
---
applyTo: "src/Services/**/*.cs"
excludeAgent: ["code-review"] # Optional: exclude specific agents
---
# Backend C# Guidelines
Use PlatformValidationResult for validation...
Prompts ()
yaml
---
mode: agent # Optional: agent, chat, edit
---
# Debug this issue
1. Analyze the error
2. Find root cause
3. Propose fix
Agent Skills ()
Folder structure with SKILL.md + bundled resources:
skills/my-skill/
├── SKILL.md
├── scripts/
├── references/
└── assets/
Chat Modes ()
Custom chat personalities with tool restrictions:
yaml
---
name: security-reviewer
tools: ["read", "grep", "glob"] # Restrict tools
---
# Security Review Mode
Focus only on security vulnerabilities...
Agents ()
Specialized agent definitions:
yaml
---
name: frontend-developer
description: UI/UX implementation specialist
---
# Frontend Developer Agent
Specializes in React, TypeScript, CSS...
Sync Patterns
Patterns for keeping Claude Code and GitHub Copilot configurations synchronized.
Skill Sync
Both platforms support skills in
. Copilot also reads
.
Best Practice: Create skills in
for maximum compatibility.
.github/skills/my-skill/
├── SKILL.md # Both platforms read
├── scripts/ # Executable scripts
├── references/ # Progressive disclosure docs
└── assets/ # Templates, images
Prompt/Command Sync
| Claude Code | GitHub Copilot |
|---|
| .github/prompts/my-cmd.prompt.md
|
| Invoked via | Invoked via or |
Sync Strategy:
- Create in (both read)
- Or maintain duplicates if behavior differs
Instructions Sync
| Claude Code | GitHub Copilot |
|---|
| (root) | .github/copilot-instructions.md
|
| Single file | Multi-file with patterns |
Sync Strategy:
- Keep core rules in both files
- Use for path-scoped rules (Copilot-specific)
- Reference detailed docs from both files
Agent Sync
Single Source: Maintain agents in
only.
Workflow Sync
Claude has workflow orchestration. Copilot uses chat modes.
| Claude Workflow | Copilot Equivalent |
|---|
| Sequential agent chains | Chat mode switching |
| |
Decision Matrix
| Feature | Location | Reason |
|---|
| Skills | | Maximum compatibility |
| Prompts | | Both platforms read |
| Agents | | Shared location |
| Instructions | Both files | Platform-specific nuances |
| Workflows | | Claude-specific |
| Chat Modes | | Copilot-specific |
Common Sync Tasks
Add New Skill
bash
mkdir -p .github/skills/new-skill
# Create SKILL.md with frontmatter
# Add references/ and scripts/ as needed
Add New Prompt
bash
# Create in .github/prompts/ for both platforms
touch .github/prompts/new-prompt.prompt.md
Update Core Instructions
- Edit
- Edit
.github/copilot-instructions.md
- Keep essential rules in sync
Add Path-Scoped Instructions (Copilot)
bash
# Copilot-specific feature
touch .github/instructions/backend-cqrs.instructions.md
# Add applyTo: "src/Services/**/*Command*.cs"
Sync Process
Step 1: Understand Current Setup
Read these files to understand current configuration:
.claude/workflows/orchestration-protocol.md
.claude/workflows/primary-workflow.md
.github/copilot-instructions.md
.github/AGENTS.md
CLAUDE.md
Step 2: Research Latest Features
Search web for:
- "GitHub Copilot features setup 2026"
- "GitHub Copilot custom instructions agents skills prompts"
- "GitHub Copilot agent mode workspace context"
See the GitHub Copilot Features Catalog section above for the full feature catalog.
Step 3: Identify Sync Opportunities
Compare capabilities and identify gaps:
- Skills missing in one platform
- Inconsistent prompt/instruction behavior
- Agent definitions that differ
Step 4: Implement Changes
For each change:
- Skills: Create in both and
- Prompts: Create in both and
- Instructions: Update both and
.github/copilot-instructions.md
- Agents: Update (shared by both)
Compatibility Notes
- Copilot reads automatically (backward compatibility)
- Both read
.github/prompts/*.prompt.md
- Both read
- Both read in root or
- Both support path-based instruction files via in frontmatter
Sources
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed