backup

Automate backing up Claude Code configuration to GitHub via Git operations.

Updated Nov 10, 2018
One-click install
npx skills add https://github.com/GLaDO8/dotfiles --skill backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backup
Source: https://github.com/GLaDO8/dotfiles/tree/main/claude/backup/skills/backup
Command: npx skills add https://github.com/GLaDO8/dotfiles --skill backup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates backing up Claude Code configuration to GitHub by detecting changes, staging them, and pushing updates to the claude-config repository.

Core Features & Use Cases

  • Check for changes in claude-config with git status
  • Show diffs and review changes
  • Stage and commit updates with a descriptive message
  • Push commits to GitHub and confirm backup
  • Gracefully handle scenarios with no changes

Quick Start

cd ~/claude-config git status --short If changes detected, review diffs: git diff then stage and commit: git add -A git commit -m "<message>" push to remote: git push Backup complete.

Frequently Asked Questions about backup

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

FAQPage Schema
How do I automatically back up Claude Code configuration to GitHub?

To back up Claude Code configuration to GitHub automatically, use a skill that detects changes in your claude-config repository, stages them with git add, commits with a descriptive message, and pushes the updates to the remote repository.

What is the process for committing and pushing claude-config file changes?

The process for committing and pushing claude-config file changes involves running git status to detect modifications, reviewing the diffs, staging all changes with git add -A, committing them, and pushing the commit to GitHub for a versioned backup.

Do I need a local Git repository to automate Claude config backups?

Yes, you need a local claude-config repository set up with Git to automate backups. The automation requires standard Git operations including status, diff, add, commit, and push to detect and upload configuration changes to GitHub.

How does the backup automation handle scenarios with no configuration changes?

The backup automation gracefully handles scenarios with no configuration changes by detecting an empty git status, skipping the staging, committing, and pushing operations, and confirming that no backup is necessary without causing errors.

Can I review configuration diffs before pushing a backup to GitHub?

Yes, you can review configuration diffs before pushing a backup to GitHub. The workflow checks for changes using git status, displays the exact modifications with git diff, and waits for your confirmation before staging and committing the updates.

What's the best way to version control Claude Code settings and skills?

The best way to version control Claude Code settings and skills is to store them in a dedicated claude-config Git repository and automate the backup process, ensuring every modification is tracked, committed with a descriptive message, and pushed to GitHub.