zhaojiannet

Cclayer — Git skill for Claude Code

Git community

Sync Claude Code config across machines: CLAUDE.md, skills, hooks, settings.json, plugins and MCP servers.

How to install Cclayer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open zhaojiannet/cclayer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cclayer does

Sync Claude Code config across machines: CLAUDE.md, skills, hooks, settings.json, plugins and MCP servers. Layered dotfiles for Claude Code with per-team git identities, a full-screen setup and an English, Chinese and Japanese interface.

Alternatives in Git

  • Fullstack Dev Skills — by jeffallan - A comprehensive Claude Code plugin with 65 specialized skills covering full-stack development a 7k ★
  • Zcf — GitHub Repo stars Zero-Config Code Flow for Claude code & Codex Zero-config workflow 5.8k ★
  • Publish MCP Server — Publishes one of the bundled MCP servers to npm 238 ★

README

cclayer

Sync your Claude Code configuration across machines: `CLAUDE.md`, rules, skills, hooks, `settings.json`, plugins and MCP servers. What belongs to one team, its git identity included, appears only in that team's projects.

[中文](README.zh.md) · [日本語](README.ja.md) · [Tutorial](docs/tutorial.en.md)

You use Claude Code on more than one machine, and your projects come from more than one team. Global rules, skills, plugins and permissions should change once and apply everywhere. Each team's git identity, rules and hooks take effect in that team's projects and on that team's machines only, and never mix into another team's.

cclayer splits the configuration into two kinds of git repositories: one **public base layer** for what is the same everywhere, and one **private overlay** per team for what belongs to it alone. A machine pulls the base plus the overlays it may see; one command applies them, one command writes local changes back.

Just your own setup

No teams to keep apart? One base layer is all you need:

cclayer setup     # give a new directory (a cloud-synced folder works) or a private git URL
cclayer capture --add CLAUDE.md --add rules/ --add skills/   # take in what this machine has

On every other machine, run `cclayer setup` with the same location and `cclayer apply` brings the configuration over. Add `private = true` under `[layer]` in the base's `layer.toml` when only you use it and it lives somewhere private: `check` then lets email addresses through. The [tutorial](docs/tutorial.en.md#4-the-simplest-setup-one-person-several-machines-directory-sync) walks through it.

How it works

A **layer** is a directory with a `layer.toml` at its root. Usually it is a git repository that cclayer clones; it can also be a plain directory on this machine, for example inside a folder your cloud drive syncs, with no git at all.

  • The base layer holds what every device gets: CLAUDE.md, rules/, skills/, output-styles/, agents/, hook