Agent skill
ai-dev-tools-sync
[AI & Tools] Synchronize and update Claude Code and GitHub Copilot development tool configurations to work similarly. Use when asked to update Claude Code setup, update Copilot setup, sync AI dev tools, add new skills/prompts/agents across both platforms, or ensure Claude and Copilot configurations are aligned. Covers skills, prompts, agents, instructions, workflows, and chat modes.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ai-dev-tools-sync-duc01226-easy-claude
SKILL.md
[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.
Quick Summary
Goal: Synchronize Claude Code and GitHub Copilot configurations to maintain feature parity across both AI dev tools.
Workflow:
- Understand — Read current configs (CLAUDE.md, copilot-instructions.md, agents, workflows)
- Research — Search for latest features across both platforms
- Compare — Identify gaps in skills, prompts, agents, or instructions
- Sync — Implement changes in both platforms maintaining compatibility
Key Rules:
- Copilot reads
.claude/skills/automatically (backward compatibility) - Both platforms read
.github/prompts/*.prompt.mdand.github/agents/*.md - Always update both
CLAUDE.mdand.github/copilot-instructions.md+.github/instructions/*.instructions.mdfor instruction changes
Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
AI Dev Tools Sync
Synchronize Claude Code and GitHub Copilot configurations to maintain feature parity.
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 | .claude/skills/ + .github/skills/ |
| SKILL.md | prompts/*.prompt.md | .claude/skills/ + .github/prompts/ |
| agents/*.md | agents/*.md | .github/agents/ (shared) |
| workflows/*.md | - | .claude/workflows/ |
| CLAUDE.md | copilot + instructions/ | Root + .github/ |
| - | chatmodes/*.chatmode.md | .github/chatmodes/ |
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/instructions/*.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 references/copilot-features.md for 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
.claude/skills/and.github/skills/ - Prompts: Create in both
.claude/skills/and.github/prompts/ - Instructions: Update
CLAUDE.md+.github/copilot-instructions.md+.github/instructions/*.instructions.md - Agents: Update
.github/agents/(shared by both)
Compatibility Notes
- Copilot reads
.claude/skills/automatically (backward compatibility) - Both read
.github/prompts/*.prompt.md - Both read
.github/agents/*.md - Both read
AGENTS.mdin root or.github/ - Both support path-based instruction files via
applyToin frontmatter
References
- Copilot Features Catalog
- Sync Patterns
IMPORTANT Task Planning Notes (MUST FOLLOW)
- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?