backup-vault

Stage, commit, and push vault changes to a git remote.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/brian-wijaya/dotfiles --skill backup-vault
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backup-vault
Source: https://github.com/brian-wijaya/dotfiles/tree/main/.claude/skills/backup-vault
Command: npx skills add https://github.com/brian-wijaya/dotfiles --skill backup-vault

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Back up ~/vault/ knowledge base to a Git remote to prevent data loss and enable versioned history for notes, specs, and organization files.

Core Features & Use Cases

  • Automatic backup workflow for changes in ~/vault using standard Git commands.
  • Versioned history and remote synchronization to protect against local data loss and enable collaboration.
  • Safe backup practices by prompting review of untracked sensitive files before committing.

Quick Start

cd ~/vault && git status cd ~/vault && git add -A cd ~/vault && git commit cd ~/vault && git push -u origin HEAD

Frequently Asked Questions about backup-vault

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

FAQPage Schema
How do I automatically back up my local notes to a git remote?

Back up vault changes by staging, committing, and pushing from the ~/vault directory. This requires a local git repository with a configured remote origin to ensure versioned, remote-safe storage and quick recovery for notes and org files.

What is the best way to version control my organization files and specs?

The best way to version control organization files and specs is backing up the ~/vault knowledge base to a git remote. This provides versioned history and remote synchronization to protect against local data loss and enable collaboration.

Do I need a local git repository to push my vault changes?

Yes, you need a local git repository with a configured remote origin to push your vault changes. The backup workflow relies on standard git commands to stage and synchronize files from the ~/vault directory to the remote.

How does this backup process handle untracked sensitive files?

The backup process handles untracked sensitive files by prompting a review before committing. It checks for untracked sensitive files in the ~/vault directory to ensure safe backup practices before pushing to the git remote.

What are the limitations of using git for vault backups?

Limitations of using git for vault backups include the requirement for a pre-configured local git repository and remote origin. The workflow depends on standard git commands and requires checking for untracked sensitive files before each commit.