sync

To sync Claude configuration files safely, run /sync to copy configurations from a central system-configs/.claude/ directory to the local ~/.claude/ environment. This process ensures deterministic synchronization and prevents configuration drift across your deployment workflow.

Preventing configuration drift during Claude deployments requires synchronizing files from a central repository to local environments with automatic backups and validation. This ensures target directories are ready and file integrity is verified before any updates are applied.

Yes, syncing Claude configs requires a source directory at system-configs/.claude/ containing your central configurations and a writable target directory at ~/.claude/ locally to receive the synchronized files.

Backup validation works by automatically creating a backup of existing files before applying changes, then verifying file integrity and checking agent and skill references during the synchronization process to ensure configurations remain valid.

Yes, you can validate agent and skill references during the sync process. The synchronization task includes basic validation that checks file integrity and verifies these references before updating the target ~/.claude/ directory.

A Claude config sync might fail if the source directory system-configs/.claude/ is missing, the target directory ~/.claude/ is not writable, or if the built-in validation detects file integrity issues or broken agent and skill references.