gitclaw

Automate OpenClaw workspace backups and sync to a GitHub repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates backing up and syncing the OpenClaw workspace to a GitHub repository, ensuring continuous backup and easy recovery.

Core Features & Use Cases

  • Deterministic, automated backups from the agent workspace to GitHub.
  • cron-driven commits and pushes to keep the remote repository up to date.
  • Silent, hands-off operation with gh-based authentication and minimal user prompts.

Quick Start

Configure a git-backed backup by naming the repository and visibility, then start hourly automated commits.

Frequently Asked Questions about gitclaw

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

FAQPage Schema
How do I automate backing up my workspace to a GitHub repository?

Automated workspace backup to GitHub uses cron-driven commits and pushes to keep a remote repository up to date. It configures repository naming, visibility, and gh-based authentication to enable silent, hands-off operation.

Can I schedule periodic workspace mirroring to Git without manual prompts?

Periodic workspace mirroring to Git operates silently using cron-based scheduling for automated commits. It requires frontmatter metadata and deterministic commit identity to ensure consistent, hands-off synchronization.

What prerequisites are needed to sync an OpenClaw workspace to GitHub?

Syncing an OpenClaw workspace to GitHub requires frontmatter metadata, GitHub authentication, repo creation, and deterministic commit identity. These prerequisites enable cron-based scheduling for automated recovery workflows.

Does GitHub authentication work with automated cron backup workflows?

GitHub authentication supports automated cron backup workflows through gh-based authentication. It enables silent operation with minimal user prompts, ensuring deterministic commits push workspace changes to the remote repository.

What's the best way to set up automated recovery workflows for my workspace?

Automated recovery workflows rely on deterministic workspace backup to GitHub via cron-driven commits. By naming the repository and setting visibility, you start hourly automated commits that ensure continuous backup and easy recovery.

Are there limitations to using cron for workspace backup and sync?

Using cron for workspace backup limits scheduling to fixed intervals like hourly automated commits. It requires deterministic commit identity and frontmatter metadata, meaning irregular sync triggers or manual recovery actions are not natively supported.