claude-config-sync

Synchronize claude-config repositories with symlink checks and security scans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users keep their personal Claude Code configuration repository in sync across machines, with safety checks and a reproducible commit workflow.

Core Features & Use Cases

  • Detects and reconciles symlinked versus standalone skill copies in the claude-config setup, ensuring drift-free synchronization.
  • Performs cleanup of residual artifacts and enforces a security scan before any commit to prevent secrets leakage.
  • Validates the README skill table when skills are added or removed, and guides users through a repeatable stage/commit/push workflow.

Quick Start

Run the configured sync workflow to detect symlinks, remove residuals, perform a security scan, update the README table, and push changes to your claude-config repository.

Frequently Asked Questions about claude-config-sync

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

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

You can sync your Claude Code configuration across machines by automating the alignment of your local claude-config repository. The workflow detects symlinks, cleans residual artifacts, and prepares commits to ensure drift-free synchronization.

What is the safest way to commit claude-config changes to git?

The safest way to commit claude-config changes to git is using a staged commit workflow. This enforces a security scan to prevent secrets leakage, validates symlinks, and updates the README table before pushing any changes.

How do I prevent secrets leakage when pushing config repositories?

To prevent secrets leakage when pushing config repositories, you should enforce a security scan before any commit. This hard-block safeguard scans your claude-config setup to ensure sensitive data is not exposed during the sync workflow.

Why does my symlinked skill copy drift from the standalone version?

Symlinked skill copies drift from standalone versions when local changes are not properly reconciled. Detecting and aligning these symlinked setups within your claude-config repository ensures drift-free synchronization across different devices.

Do I need to manually update the README skill table when adding or removing skills?

You do not need to manually update the README skill table when adding or removing skills. The sync workflow automatically validates and updates the README table as part of the automated commit preparation process.