gitclaw-backup

Automate GitHub backups of the OpenClaw workspace with versioned restorable copies.

55|5|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/blessonism/openclaw-skills --skill gitclaw-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitclaw-backup
Source: https://github.com/blessonism/openclaw-skills/tree/main/gitclaw-backup
Command: npx skills add https://github.com/blessonism/openclaw-skills --skill gitclaw-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates GitHub backups of the OpenClaw workspace to ensure versioned, restorable copies and protect against data loss.

Core Features & Use Cases

  • Automated daily or on-demand backups of the OpenClaw workspace to a GitHub repository.
  • Lock-based synchronization that respects .gitignore and skips when there are no changes.
  • Logging and status checks to monitor backup health and history.

Quick Start

Run the backup script to synchronize your OpenClaw workspace to GitHub.

Frequently Asked Questions about gitclaw-backup

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

FAQPage Schema
How do I automate GitHub backups for my workspace?

Automated GitHub backups synchronize your workspace to a repository using a local backup script and a cron schedule, ensuring versioned, restorable copies without manual intervention.

Can I run on-demand workspace backups in addition to scheduled syncs?

On-demand workspace backups can be triggered manually alongside daily cron schedules, using a lock mechanism to prevent concurrent runs and logging each backup activity for audit trails.

Does the backup process respect .gitignore when pushing to GitHub?

The backup process respects .gitignore configurations and skips pushing when there are no detected changes, ensuring only relevant workspace updates sync to the GitHub origin main branch.

What do I need to set up before automating workspace backups to GitHub?

Setting up workspace backups requires a GitHub repository, a local backup script, and either a cron schedule or manual execution to push versioned copies and monitor status checks.

How do I monitor backup health and audit trails for my GitHub syncs?

Backup health and audit trails are monitored through built-in logging and status checks, which record each sync activity and provide history to verify successful workspace pushes to GitHub.

Why does my scheduled workspace backup skip pushing to GitHub?

Scheduled workspace backups skip pushing to GitHub when the lock-based synchronization detects no changes in the workspace, avoiding unnecessary commits and keeping the backup history clean.