Trying to figure out how teams run Claude Code with a shared baseline (agents, skills, commands, CLAUDE.md) when multiple people are using and improving it in parallel. Central ops maintains a canonical .claude/ setup, everyone pulls it from Git. The actual problem isn’t that the setup drifts per user — drift can be good. When someone hits an edge case and tweaks a skill or refines an agent prompt to fix it, that’s a real improvement I want to keep. The problem is that those changes happen locally with zero documentation or traceability. Nobody else benefits from the fix, I can’t see what was changed or why, and a week later every team member has silently diverged. When I push a central update, it either overwrites useful local fixes or conflicts in ways nobody can resolve. After a while it’s just chaos. I’m not looking for a read-only mode — I want individual adaptation to keep happening, that’s where the real-world improvements come from. What I’m missing is a workflow with Git-like semantics for a setup that mutates itself during normal use: local changes that are diffable, good ones that can flow back to the central repo as something like a PR, central updates that pull cleanly without nuking local improvements, and some audit trail of why a skill or agent prompt changed. Has anyone built something like this, or landed on conventions that work? Especially curious how you separate personal scratch config from team-shareable improvements, and whether anyone wraps Claude Code in a layer that logs or diffs config mutations automatically. submitted by /u/itsbloomberg
Originally posted by u/itsbloomberg on r/ClaudeCode