sync

Commit local ~/.claude changes, pull with rebase, and push to the remote repository.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/andreiverdes/awesome-claude --skill sync-andreiverdes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/andreiverdes/awesome-claude/tree/main/skills/sync
Command: npx skills add https://github.com/andreiverdes/awesome-claude --skill sync-andreiverdes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the hassle of keeping your local Claude Code configuration in sync with a shared remote git repository so you don’t lose updates or overwrite changes across machines.

Core Features & Use Cases

  • Commit local Claude Code changes: Captures updates to settings, skills, and memories stored under ~/.claude.
  • Pull with rebase and resolve conflicts: Handles remote divergence by guiding resolution for settings.json, memory files, and skills.
  • Push the merged result: Publishes the synchronized state back to the remote so all machines and collaborators converge.
  • Use Case: You update skills and memories on your laptop, then switch to your desktop and want a reliable way to sync everything without manual git babysitting.

Quick Start

Run the sync flow when you want to sync your Claude Code config from your current machine to the remote repo with commit, pull+rebase, and push.

Frequently Asked Questions about sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Claude Code configuration across multiple machines?

Syncing Claude Code configuration involves committing local ~/.claude changes, pulling with rebase to integrate remote updates, and pushing the merged result. This process ensures settings, skills, and memories stay consistent across all machines.

What is the best way to resolve git rebase conflicts for dotfiles like settings.json?

Resolving git rebase conflicts for dotfiles like settings.json requires manual conflict resolution during the pull --rebase step. The sync process guides you through resolving divergent changes in memory files, settings, and skills before completing the push.

Can I use a portable setup for Claude Code without manual git babysitting?

Yes, a portable setup for Claude Code is achieved by synchronizing your ~/.claude directory with a shared remote repository. One command commits, rebases, and pushes updates, eliminating manual git babysitting across your laptop and desktop.

Do I need a remote origin setup to synchronize my Claude Code dotfiles?

Yes, you need a remote git origin configured for your ~/.claude directory to synchronize dotfiles. The sync process requires remote verification or origin setup to pull updates and push converged configuration states across machines.

Why does pulling with rebase help manage configuration management for Claude Code?

Pulling with rebase helps manage configuration management for Claude Code by integrating remote updates cleanly without merge commits. It identifies divergent changes in settings and memory files, providing guidance to resolve conflicts before pushing.