Claude Code Team Sync — Git skill for Claude Code
Share Claude Code sessions, notes and team context with coworkers: hand over, load or resume a teammate's session through a git branch, a git repo or a synced folder (OneDrive, SharePoint, Teams, Goog.
How to install Claude Code Team Sync
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open nrzz/claude-code-team-sync and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Claude Code Team Sync does
Share Claude Code sessions, notes and team context with coworkers: hand over, load or resume a teammate's session through a git branch, a git repo or a synced folder (OneDrive, SharePoint, Teams, Google Drive).
Alternatives in Git
README
Claude Code team sync
[](https://github.com/nrzz/claude-code-team-sync/actions/workflows/test.yml) [](LICENSE)   [](https://github.com/nrzz/claude-code-toolkit)
Work on one project with your coworkers in Claude Code without starting from zero every time. Share the session you are in with one command, pick up a teammate's session where they left it, and give every new session the team's notes and decisions before anyone types a word.
Each person keeps their own Claude seat (Team, Enterprise, Pro, Max or an API key). Nothing here shares a login. What travels is context.
Why this exists
Claude Code keeps every conversation on the machine it ran on. A Team plan gives each person a seat, not a shared history, and Claude Code has no built-in way to hand a local session to a teammate. Git already carries the shared parts of a project's setup (`CLAUDE.md`, `.claude/settings.json`, skills). This adds what was missing:
| You want to | Without this | With this |
|---|---|---|
| Hand over a half-done task | Write a long Slack message, or paste the whole chat | /team-share: Claude writes the brief, the session goes to the hub |
| Continue a teammate's work | Re-explain everything to a fresh session | /team-load login bug: their brief and conversation load into yours |
| Continue their exact session | Not possible | claude-team resume : their transcript becomes your own session |
| Keep the team on the same page | Hope everyone reads the wiki | Notes and TEAM.md reach every new session by themselves |
What it costs in tokens
Every team member pays
Related Skills
Git Dupe
A second Git repo inside .git for the files that are yours, not the project's (.env.local, notes, your own CLA
Yogit
A git-native mailbox for coding-agent sessions (Claude Code, Codex, Cursor, humans): letters live as refs, syn
Mega
Turn a multi-objective destination into a sequenced roadmap of dependent sub-goals: decompose, front-load ever
Next Ticket
Ingest the next ticket FROM THE WORKTREE'S BOUND PROJECT — set up its branch, move In Progress, load context,
Lane Ops
Continuity and orchestration lane. Own the loop, the lane machinery, the merge gate, and the durable record th
Release Noter
Generates user-friendly release notes from git commits and PRs with audience-specific tone adjustment (users,
Related Agents
Envoy Runner
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper roo
Powersync Sync Reviewer
Use to review any change that touches PowerSync synced tables before merging — diffs that modify shared/powers
Asset Manager
Publish and manage hosted assets (HTML sites, docs, file bundles) on the Octave assets service. Use when the u
