settings-restore

Restores Claude Code settings from a backup git repository to ~/.claude/ with verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving Claude Code settings to a new machine or recovering them after a reset is error-prone when done by hand — files get missed, executable bits on hooks are lost, and local files can be silently deleted. This Skill restores settings from a dedicated backup git repository with a preview, confirmation, and post-restore verification. ## Core Features & Use Cases - Flexible source resolution: Accepts a local repo path or a clone URL, cloning to ~/.claude-settings-backup on new machines, with credential redaction in all output. - Diff preview and confirmation: Shows added, modified, unchanged, and deleted files per entry before any changes, requiring explicit interactive approval. - Verified restore with safety checks: Mirrors the backup into ~/.claude/ via rsync or cp fallback, then re-compares every restored entry and checks hook execute bits, reporting any failures. - Use Case: You get a new laptop and want your Claude Code configuration back. Point the Skill at your backup repo URL, review the diff preview, confirm, and get a verified restore with a note to restart Claude Code. ## Quick Start Ask the assistant to restore your Claude Code settings from your backup repository URL, for example by saying: restore my settings from https://github.com/you/claude-settings-backup.git.

Frequently Asked Questions about settings-restore

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

FAQPage Schema
How do I restore Claude Code settings on a new machine?▼

Pass the clone URL of your backup repository to the restore workflow. It clones the repo to ~/.claude-settings-backup, previews the changes, and copies files into ~/.claude/ after your confirmation.

How do I restore settings from a local backup repo path?▼

Provide the local path as an argument or store it as repoPath in ~/.claude/settings-sync.json. The path must be a valid git repository; otherwise the restore stops with guidance to pass a clone URL instead.

Does restoring settings delete local files not in the backup?▼

Yes. Directory entries are mirrored with rsync --delete or an rm -rf plus cp fallback, so local files absent from the backup are removed. The diff preview lists these as deleted before you confirm.

Is settings.local.json restored automatically?▼

No. settings.local.json is restored only when ~/.claude/settings-sync.json exists and sets includeLocalSettings to true. On a new machine without that config file, it is skipped by default.

Why does the restore reject plain http:// clone URLs?▼

Restored hooks scripts are executed by Claude Code on next start, so an unencrypted clone is a code-injection risk. Cloning over http:// requires explicit confirmation and is stopped if declined.

When should I not use settings restore?▼

Do not use it to back up settings — that is the settings-backup workflow — or to compare settings without making changes. It also cannot run non-interactively because confirmation is always required.