project-sync

Synchronize Claude Code configurations across Codex, Gemini, and Copilot CLI.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill project-sync-kaiohenricunha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-sync
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/project-sync
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill project-sync-kaiohenricunha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually replicating repo-local agent configurations (commands, skills, rule files) across Claude Code, Codex, Gemini, and Copilot CLI is tedious, error-prone, and leads to inconsistent workflows when working with multiple agentic tools.

Core Features & Use Cases

  • Cross-CLI Artifact Fan-Out: Automatically maps .claude/commands and .claude/skills to the correct discovery paths for Codex, Gemini, and Copilot, eliminating manual file copying.
  • Rule Floor Refresh: Updates AGENTS.md, GEMINI.md, and .github/copilot-instructions.md directly from your project's shared rule floor to keep cross-CLI instructions in sync.
  • Drift Detection: Includes a built-in check to verify sync status and surface missing or stale files across all supported CLIs.
  • Use Case: For example, if you add a new slash command to .claude/commands/, this skill automatically makes it available in Copilot as a .prompt.md file and in Codex/Gemini as a skill with a single invocation.

Quick Start

Use the project-sync skill to fan out your repo's existing Claude commands and skills to Codex, Gemini, and Copilot, and refresh all cross-CLI rule instruction files.

Frequently Asked Questions about project-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Claude Code commands and skills to Codex, Gemini, and Copilot CLI?

To sync Claude Code commands and skills, you can automate cross-CLI artifact fan-out to map configurations directly into the correct discovery paths for Codex, Gemini, and Copilot. This eliminates manual file copying and ensures consistent agentic workflows across all platforms.

What is the best way to keep AGENTS.md and GEMINI.md rule files updated across multiple agentic CLIs?

Keeping AGENTS.md and GEMINI.md updated requires a rule floor refresh mechanism that automatically regenerates cross-CLI instruction files from a shared source. This ensures all agentic tools receive identical project rules without manual replication.

Does Copilot CLI support Claude Code slash commands automatically?

Copilot CLI does not natively support Claude Code slash commands, but cross-CLI sync tools can map .claude/commands into Copilot-compatible .prompt.md files. This allows a single command definition to be deployed across both platforms instantly.

How can I detect configuration drift between Claude Code and Gemini CLI?

To detect configuration drift between Claude Code and Gemini CLI, you can run a built-in sync status check that surfaces missing or stale files across discovery paths. This verifies that your cross-CLI agent configurations remain consistent over time.

Why do my Codex CLI skills keep diverging from my Claude Code repository configurations?

Codex CLI skills diverge from Claude Code configurations when repo-local agent artifacts are copied manually without automated cross-CLI sync. Implementing an automated fan-out process maps your source commands directly to Codex discovery paths, preventing stale files.