Get the FREE Ultimate OpenClaw Setup Guide →

Backup Config

npx machina-cli add skill OhJuhun/claude-backup-sync/backup-config --openclaw
Files (1)
SKILL.md
454 B

Backup Config

Manually sync Claude Code config to GitHub backup repository.

Trigger

User says: "backup config", "sync config", "push config", "/backup-config"

Steps

Run the backup sync script:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/backup-sync.sh"

Report the result to the user in Korean.

If successful, show:

  • Number of files synced
  • Target repository name

If no changes detected, tell the user there are no changes to sync.

Source

git clone https://github.com/OhJuhun/claude-backup-sync/blob/main/skills/backup-config/SKILL.mdView on GitHub

Overview

Back up Claude Code configuration to a GitHub backup repository to preserve versioned, recoverable settings. This skill runs a dedicated backup-sync script and reports results in Korean, including how many files were synced and the target repository name. It helps maintain config integrity and simplifies disaster recovery.

How This Skill Works

When the user says backup config, sync config, push config, or /backup-config, the plugin executes the backup-sync.sh script located at CLAUDE_PLUGIN_ROOT/scripts/backup-sync.sh. The script pushes changes to the backup repository and returns a summary, which is shown to the user in Korean; if there are changes, it includes the number of files synced and the repository name, otherwise it reports no changes.

When to Use It

  • Before major Claude Code upgrades to capture the current config
  • After adjusting settings to back up the latest configuration
  • When collaborating with teammates who need a central backup
  • For disaster recovery and audit readiness of Claude Code config
  • On-demand backups prior to deployment or maintenance windows

Quick Start

  1. Step 1: Run the backup script: bash ${CLAUDE_PLUGIN_ROOT}/scripts/backup-sync.sh
  2. Step 2: Wait for the script to finish and generate the Korean result
  3. Step 3: Review the result for the number of files synced and the target repository name (or note if no changes)

Best Practices

  • Verify the CLAUDE_PLUGIN_ROOT path and that backup-sync.sh is executable
  • Ensure the GitHub backup repository is accessible and permissions are set
  • Check for actual changes before triggering to avoid empty commits
  • Validate and report the exact target repository name in the results
  • Always return the outcome in Korean to match user expectations

Example Use Cases

  • Backup succeeds: 12 files synced to claude-config-backups.
  • No changes detected; no files were synced.
  • After updating settings, 4 files synced to claude-code-configs.
  • Nightly backup runs automatically; 3 files synced to nightly-claude-config.
  • Manual trigger: backup-config returns success with repo name and file count.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers