DazzleML

Dazzle Claude Config Sync — Git skill for Claude Code

Git community

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

[![PyPI](https://img.shields.io/pypi/v/dazzle-claude-config?color=green)](https://pypi.org/project/dazzle-claude-config/) [![Release Date](https://img.shields.io/github/release-date/DazzleML/dazzle-claude-config?color=green)](https://github.com/DazzleML/dazzle-claude-config/releases) [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/) [![License: GPL v3](https://img.shields.io/badge/license-GPL%20v3-green.svg)](https://www.gnu.org/licenses/gpl-3.0.html) [![Installs](https://img.shields.io/endpoint?url=https://gist.githubusercontent.com/djdarcy/5329fbe75d9bbd8597cdc45863a22878/raw/installs.json)](https://dazzleml.github.io/dazzle-claude-config/stats/#installs) [![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20Linux%20%7C%20macOS%20%7C%20BSD-lightgrey.svg)](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**