backup

Commit and push engine and data repositories to GitHub with secret scanning.

10|1|Updated Jun 29, 2026

Search Tags:#git #security #github #workspace #backup #sync

Ready to run

npx skills add https://github.com/mishahanin/heading-os --skill backup-mishahanin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backup
Source: https://github.com/mishahanin/heading-os/tree/main/.claude/skills/backup
Command: npx skills add https://github.com/mishahanin/heading-os --skill backup-mishahanin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the risk of data loss by providing a robust, automated mechanism to commit and push both the engine and data repositories to GitHub, ensuring your executive workspace is always backed up off-machine.

Core Features & Use Cases

Two-Part Topology Sync: Automatically handles the separation between the engine code and the private data overlay.
Security-First Verification: Performs pre-push secret scanning and ahead/behind verification to prevent accidental leaks or data loss.
Use Case: Use this at the end of a work session to ensure all your CRM updates, knowledge base changes, and operational threads are safely pushed to your private GitHub repository.

Quick Start

Execute the backup skill to commit and push all workspace changes to your remote repository.

Frequently Asked Questions about backup

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

FAQPage Schema

How do I automatically sync my local workspace to GitHub?▼

To sync your local workspace to GitHub, this skill automates commit and push operations for both engine and data repositories. It handles the two-part topology separation and performs pre-push secret scanning to ensure secure version control.

Does GitHub backup include secret scanning before pushing changes?▼

GitHub backup includes pre-push secret scanning to prevent accidental leaks. It verifies repository state and performs ahead/behind checks before pushing your workspace changes to the remote origin.

How do I back up my executive workspace repositories off-machine?▼

You can back up executive workspace repositories off-machine by running this skill to commit and push all changes to GitHub. It syncs both engine code and private data overlays, ensuring data integrity and redundancy.

Do I need Python3 to sync local repositories with GitHub?▼

Python3 is required to run the scripts that sync local repositories with GitHub. The skill uses Python3 to manage the two-part engine and data topology, perform secret scanning, and execute automated push operations.

What is the best way to manage two-part topology sync for workspace repositories?▼

The best way to manage two-part topology sync is using automated commit and push operations that separate engine code from private data. This approach verifies repository state and scans for secrets before pushing to GitHub.

Why does my workspace backup fail before pushing to GitHub?▼

Workspace backup may fail during pre-push verification if the repository state check detects issues or if secret scanning finds sensitive data. The skill performs ahead/behind verification to prevent data loss before executing push operations.