settings-backup

Backs up Claude Code user settings to a git repository with commit and push.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill settings-backup-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: settings-backup
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/settings-sync/skills/settings-backup
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill settings-backup-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Claude Code user settings (settings.json, CLAUDE.md, commands, skills, hooks, agents) live only on the local machine and are lost on hardware failure or when moving to a new machine. This Skill copies them into a dedicated git repository, commits real changes, and pushes them, including unattended runs as a scheduled routine. ## Core Features & Use Cases - Git-based backup: Copies user-authored config files and directories into a git repo, commits only when something actually changed, and pushes to a remote if one exists. - Secret scanning: Greps every backup source for API keys and tokens (sk-, ghp_, AKIA, xoxb-, and more) and warns before pushing, or logs the finding in routine mode. - Routine-compatible: Resolves the repo path from an argument, ~/.claude/settings-sync.json, or an interactive prompt, and degrades gracefully when running unattended. - Use Case: Schedule a daily routine that backs up your Claude Code configuration so a new laptop can be restored from the repo with the companion settings-restore skill. ## Quick Start Ask Claude to back up your Claude Code settings to your backup git repository, optionally providing the repo path.

Frequently Asked Questions about settings-backup

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

FAQPage Schema
How do I back up my Claude Code settings to git?▼

Run the settings-backup skill with a repo path argument or set repoPath in ~/.claude/settings-sync.json. It copies settings.json, CLAUDE.md, and config directories into the repo, commits real changes, and pushes to the remote.

Which Claude Code config files are included in the backup?▼

The backup covers settings.json, CLAUDE.md, keybindings.json, and the rules, commands, skills, hooks, agents, output-styles, scripts, and reference directories. settings.local.json is included only when includeLocalSettings is true in the sync config.

Does the backup scan for API keys before pushing?▼

Yes, every run greps all sources for secret patterns like sk-, ghp_, AKIA, xoxb-, and Slack webhook URLs. Interactively it asks whether to continue, skip flagged files, or cancel; in routine mode it logs the finding to .sync-log and continues.

Can this skill run unattended as a scheduled routine?▼

Yes, it is designed for routine execution when repoPath is configured in ~/.claude/settings-sync.json. Without a configured path or an existing repo directory it prints an explanatory message and stops instead of prompting.

What happens when a backup push fails due to a conflict?▼

The skill reports that another machine may have pushed since the last sync and instructs you to run git pull --rebase and push manually. It never auto-resolves push conflicts.

When should I not use settings-backup?▼

Do not use it to restore settings from a backup; use the settings-restore skill instead. It also is not meant for comparing local versus backed-up settings without making changes.