Dazzle Claude Config Sync — Git skill for Claude Code
Sync Claude Code configuration across machines (ccs): collect, apply, bootstrap from a GitHub payload repo.
How to install Dazzle Claude Config Sync
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open DazzleML/dazzle-claude-config-sync and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Dazzle Claude Config Sync does
Sync Claude Code configuration across machines (ccs): collect, apply, bootstrap from a GitHub payload repo.
Alternatives in Git
- Superclaude — by SuperClaude-Org - A versatile configuration framework that enhances Claude Code with specialized commands 21.7k ★
- Zcf — GitHub Repo stars Zero-Config Code Flow for Claude code & Codex Zero-config workflow 5.8k ★
- Ccometixline - Claude Code Statusline — by Haleclipse - A high-performance Claude Code statusline tool written in Rust with Git integration, usage tra 2.3k ★
README
dazzle-claude-config-sync
[](https://pypi.org/project/dazzle-claude-config/) [](https://github.com/DazzleML/dazzle-claude-config/releases) [](https://www.python.org/downloads/) [](https://www.gnu.org/licenses/gpl-3.0.html) [](https://dazzleml.github.io/dazzle-claude-config/stats/#installs) [](docs/platforms.md)
**Git-backed sync for your Claude Code configuration (skills, commands, agents, hooks, and `CLAUDE.md`) across every machine you work on, with credential protection on the way in and backups on every write.**
The Problem
Your Claude Code setup is your workflow. It tracks how your understanding and how your projects changes over time. Skills you refined over months, agents that encode how you actually work, a `CLAUDE.md` tuned by a hundred small corrections. All of it lives in `~/.claude` on **one** machine.
Then you get a laptop. Or a work box. Or you reinstall. So you copy the folder by hand -- and now the two drift apart, silently, because there is nothing to tell you which one is newer. Worse, `~/.claude` is not only config: it also holds `.credentials.json`, OAuth state, plugin caches, and session databases. Copy it wholesale into a git repo to "back it up" and you have published an API key. There is no history either, so when a config change makes Claude behave oddly, there is nothing to diff and nothing to roll back to.
*dazzle-claude-config* (aka **ccs** or **C**laude **c**onfig **s**
Related Skills
Cclayer
Sync Claude Code config across machines: CLAUDE.md, skills, hooks, settings.json, plugins and MCP servers. Lay
Claude Code Sync
Secure cross-platform CLI to sync Claude Code configs (~/.claude/) across machines via GitHub with age encrypt
Cpv Batch Caching Optimize
Fan out cpv-cache-optimizer-agent across every plugin in a marketplace, a list of plugins, or a single plugin
Agents System Setup
Bootstrap, update, improve, or replicate multi-agent systems across GitHub Copilot CLI, Claude Code, OpenCode,
Adversarial Review
, humanizer, update_config), custom status bar, MCP integration, and a self-improvement loop that remembers co
Adopt Dannflow
Bootstrap an existing repo into a first-class DannFlow project. Installs CI (and proves it passes), creates th
Related Agents
Brain Merge
Semantically merge brain knowledge from multiple Claude Code machines. Use when brain-sync or brain-join detec
Qp Bug Hunter
Read-only reviewer for the quality-pass bugs dimension — logout teardown, reconnect state machines, token refr
C2 Operator
Command and control infrastructure specialist for authorized red team operations. Handles Sliver C2 framework,