SKILL.md

SKILL.md markdown

---
name: settings-backup
description: "Backs up Claude Code user settings to a git repo. Commits and pushes config files unattended; routine-compatible. Use when the user asks to back up or sync their Claude Code settings."
allowed-tools: Bash, Read, Write, Edit, AskUserQuestion
argument-hint: "[repo-path]"
---

# Settings Backup

Back up Claude Code user settings to a dedicated git repository. Copies
user-authored configuration files, commits, and pushes. Designed to run
unattended as a Claude routine when the repo path is configured.

## When not to use

- To restore settings from a backup — use `settings-restore` instead.
- To compare local vs backed-up settings without changing anything.

## Reference

shawn-sandy/agentics

Social media post

Most developers version-control their code. Few version-control their AI assistant configuration.

The settings-backup skill in the settings-sync plugin changes that. One command commits your Claude Code setup — settings.json, CLAUDE.md rules, custom skills, keybindings — to a dedicated git repo and pushes.

What makes it practical:
→ Routine-compatible: schedule it unattended, zero prompts
→ Conflict-aware: detects multi-machine push conflicts and tells you exactly how to resolve
→ First-backup secret scan: checks settings.json for leaked keys before anything hits git history
→ Selective sync: opt-in flag for settings.local.json to keep machine-specific config separate

The backup covers everything you've customized — the rules that shape Claude's behavior, the commands you've built, the skills you've installed. Lose nothing on a machine wipe or device swap.

If you're treating your AI config as throw-away state, you're accumulating invisible technical debt.

More automation patterns coming — follow for the next one.

#ClaudeCode #DeveloperTools #AIAutomation #DevEx