How do I install the Memory Git Sync skill?

Run npx skillmds@latest add johnalbertini14-glitch/memory-git-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memory Git Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memory Git Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memory Git Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Memory Git Sync?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memory Git Sync by johnalbertini14-glitch

Name: Memory Git Sync
Rating: 4.666666666666667 (3 reviews)
Author: johnalbertini14-glitch

Memory Git Sync

Automates the backup of the OpenClaw workspace to a remote Git repository. Handles large file exclusions, validates git configuration, and performs intelligent sync with conflict resolution.

johnalbertini14-glitch Updated Sep 21, 2026 1 repo stars

File contents

Memory Sync Skill

Automates Git synchronization and backup of workspace memory to a remote repository.

Quick Start

bash ./scripts/sync.sh [COMMIT_MESSAGE]

Default message: chore: memory backup YYYY-MM-DD HH:MM

What It Does

Validates Git repository, user config, and remote access
Detects & excludes large files (>95MB) to prevent push failures
Stages all changes automatically
Pulls latest remote changes to avoid conflicts
Commits changes with timestamped or custom message
Pushes to remote, setting upstream if needed

Prerequisites

✓ Git repository initialized with origin remote ✓ git config user.name and git config user.email set ✓ Network access to remote repository ✓ Write permissions on repository directory

Execution Steps

Step	Action	Success Output	Failure Output	Exit
1	Validate Git repo	`[SUCCESS] Git repository found`	`[ERROR] Not inside a git repository`	1
2	Check Git config	`[SUCCESS] Git user configuration is valid`	`[ERROR] Git user.name not configured`	1
3	Check remote	`[SUCCESS] Remote 'origin' configured: [URL]`	`[ERROR] No 'origin' remote`	1
4	Setup .gitignore	`[SUCCESS] Gitignore file is ready`	-	-
5	Scan large files	`[SUCCESS] No large files detected`	`[WARNING] Large files detected`	-
6	Detect changes	`[SUCCESS] All changes staged`	`[INFO] No uncommitted changes`	0
7	Fetch remote	`[SUCCESS] Successfully fetched`	`[WARNING] Fetch failed (continues)`	-
8	Check sync	`[INFO] Local and remote synchronized`	`[WARNING] Branches diverged (auto-pull)`	1*
9	Commit	`[SUCCESS] Changes committed`	`[ERROR] Commit failed`	1
10	Push	`[SUCCESS] Successfully pushed`	`[WARNING] No upstream (tries to set)`	1**
Done	Complete	`[SUCCESS] Sync completed`	-	0

*Auto-resolves with git pull --no-edit **Auto-sets upstream with git push --set-upstream origin [branch]

Output Format

All messages use structured prefixes for LLM parsing:

[INFO]    - Informational messages
[SUCCESS] - Actions completed successfully
[WARNING] - Non-fatal issues (script recovers)
[ERROR]   - Fatal errors (requires intervention)

Common Scenarios

Issue	Output	Resolution
Not in a Git repo	`[ERROR] Not inside a git repository`	Navigate to repo: `cd /path/to/repo`
Missing user.name	`[ERROR] Git user.name not configured`	`git config user.name "Name"`
Missing user.email	`[ERROR] Git user.email not configured`	`git config user.email "email@example.com"`
No origin remote	`[ERROR] No 'origin' remote configured`	`git remote add origin <URL>`
Large files detected	`[WARNING] Large files detected`	Automatically added to .gitignore
Pull conflicts	`[ERROR] Pull encountered conflicts`	Resolve manually, then run sync again
Network failures	`[WARNING] Fetch/Push failed`	Check connectivity, script continues locally

Features

Auto Large-File Handling: Prevents Git failures by ignoring files >95MB
Conflict Resolution: Auto-pulls remote before pushing
Upstream Setup: Auto-configures tracking on first push
Validation: Pre-flight checks prevent common errors
LLM-Compatible Output: Structured logs for easy parsing

Security Notes

Don't commit credentials to the repository
Use SSH keys or credential helpers: git config credential.helper osxkeychain
Review changes before syncing: git status
Large files already pushed can't be auto-removed by this script

---name: memory-git-syncdescription: Automates the backup of the OpenClaw workspace to a remote Git repository. Handles large file exclusions, validates git configuration, and performs intelligent sync with conflict resolution.---# Memory Sync SkillAutomates Git synchronization and backup of workspace memory to a remote repository.## Quick Start```bashbash ./scripts/sync.sh [COMMIT_MESSAGE]```Default message: `chore: memory backup YYYY-MM-DD HH:MM`## What It Does1. **Validates** Git repository, user config, and remote access2. **Detects & excludes** large files (>95MB) to prevent push failures3. **Stages** all changes automatically4. **Pulls** latest remote changes to avoid conflicts5. **Commits** changes with timestamped or custom message6. **Pushes** to remote, setting upstream if needed## Prerequisites✓ Git repository initialized with `origin` remote✓ `git config user.name` and `git config user.email` set✓ Network access to remote repository✓ Write permissions on repository directory## Execution Steps| Step | Action | Success Output | Failure Output | Exit ||------|--------|---|---|---|| 1 | Validate Git repo | `[SUCCESS] Git repository found` | `[ERROR] Not inside a git repository` | 1 || 2 | Check Git config | `[SUCCESS] Git user configuration is valid` | `[ERROR] Git user.name not configured` | 1 || 3 | Check remote | `[SUCCESS] Remote 'origin' configured: [URL]` | `[ERROR] No 'origin' remote` | 1 || 4 | Setup .gitignore | `[SUCCESS] Gitignore file is ready` | - | - || 5 | Scan large files | `[SUCCESS] No large files detected` | `[WARNING] Large files detected` | - || 6 | Detect changes | `[SUCCESS] All changes staged` | `[INFO] No uncommitted changes` | 0 || 7 | Fetch remote | `[SUCCESS] Successfully fetched` | `[WARNING] Fetch failed (continues)` | - || 8 | Check sync | `[INFO] Local and remote synchronized` | `[WARNING] Branches diverged (auto-pull)` | 1* || 9 | Commit | `[SUCCESS] Changes committed` | `[ERROR] Commit failed` | 1 || 10 | Push | `[SUCCESS] Successfully pushed` | `[WARNING] No upstream (tries to set)` | 1** || Done | Complete | `[SUCCESS] Sync completed` | - | 0 |*Auto-resolves with `git pull --no-edit`**Auto-sets upstream with `git push --set-upstream origin [branch]`## Output FormatAll messages use structured prefixes for LLM parsing:```[INFO] - Informational messages[SUCCESS] - Actions completed successfully[WARNING] - Non-fatal issues (script recovers)[ERROR] - Fatal errors (requires intervention)```## Common Scenarios| Issue | Output | Resolution ||-------|--------|-----------|| Not in a Git repo | `[ERROR] Not inside a git repository` | Navigate to repo: `cd /path/to/repo` || Missing user.name | `[ERROR] Git user.name not configured` | `git config user.name "Name"` || Missing user.email | `[ERROR] Git user.email not configured` | `git config user.email "email@example.com"` || No origin remote | `[ERROR] No 'origin' remote configured` | `git remote add origin <URL>` || Large files detected | `[WARNING] Large files detected` | Automatically added to .gitignore || Pull conflicts | `[ERROR] Pull encountered conflicts` | Resolve manually, then run sync again || Network failures | `[WARNING] Fetch/Push failed` | Check connectivity, script continues locally |## Features- **Auto Large-File Handling**: Prevents Git failures by ignoring files >95MB- **Conflict Resolution**: Auto-pulls remote before pushing- **Upstream Setup**: Auto-configures tracking on first push- **Validation**: Pre-flight checks prevent common errors- **LLM-Compatible Output**: Structured logs for easy parsing## Security Notes- Don't commit credentials to the repository- Use SSH keys or credential helpers: `git config credential.helper osxkeychain`- Review changes before syncing: `git status`- Large files already pushed can't be auto-removed by this script

Frequently asked questions