git-version-control

Files (3)

• origin.json · .clawhub/
• SKILL.md
• _meta.json

SKILL.md (first lines)

# Git Version Control | OpenClaw Configuration Protection

> Protect your OpenClaw environment with git-based checkpoints and rollback capability.

## Overview

OpenClaw configuration directory (`~/.openclaw/`) is a git repository. This skill provides safe version control for system configuration changes.

**Protected files include**:
- `workspace/SOUL.md`, `AGENTS.md`, `USER.md`, `IDENTITY.md`
- `workspace/skills/` - installed skills
- `workspace/memory/` - memory files
- `openclaw.json` - main configuration
- `cron/jobs.json` - cron jobs

**Excluded from version control**:
- Session logs (`*.jsonl`, `*.jsonl.lock`)
- SQLite databases (`*.sqlite`)
- Temporary files
- Credentials (sensitive)

---

## Core Operations

### 1. SAVE - Create Checkpoint

Create a git commit before making sensitive changes. This provides a recovery point.

**When to use**:
- Before modifying core configuration files
- Before installing/uninstalling skills
- Before making bulk memory changes
- User explicitly requests a save point

**Command Flow**:
```bash
cd ~/.openclaw

# Check current status
git status

# Add all tracked files (respecting .gitignore)
git add -A

# Create commit with descriptive message
git commit -m "checkpoint: {description of pending change}"
```

**Implementation**:
```
When user says: "save before..." or "create checkpoint"

1. Generate descriptive commit message based on context
2. Run: git add -A
3. Run: git commit -m "checkpoint: {description}"
4. Report commit hash and file count to user
```

**Example**:
```
User: "Save before I install a new skill"
Action:
  git add -A
  git commit -m "checkpoint: before installing new skill"
Output: "✓ Checkpoint created: abc1234 (5 files changed)"
```

---

### 2. ROLLBACK - Restore Previous State

Revert to a previous commit when issues occur.

**When to use**:
- User reports system issues after recent changes
- User explicitly requests rollback
- Configuration corruption detected
- After a failed skill installation

**Rollback Options**:

| Option | Command | Effect |
|--------|---------|--------|
| Soft reset | `git reset --soft HEAD~1` | Undo commit, keep changes staged |
| Mixed reset | `git reset --mixed HEAD~1` | Undo commit, keep changes unstaged |
| Hard reset | `git reset --hard HEAD~1` | Completely undo commit and changes |

**Recommended default**: `--hard` for full rollback

**Implementation**:
```
When user says: "rollback" or "undo last change" or "restore previous"

1. Show recent commits for user to choose
   git log --oneline -10
   
2. Confirm which commit to restore to
   "Rollback to commit X? This will discard: {list changes}"
   
3. Execute rollback
   git reset --hard {commit-hash}
   
4. Report result
   "✓ Rolled back to commit abc1234"
```

**Example**:
```
User: "Rollback to before the skill installation"
Action:
  git log --oneline -5
  # Show: abc1234 checkpoint: before skill install
  #       def5678 previous config
  git reset --hard abc1234
Output: "✓ Rolled back to 'before skill install' (abc1234)"
```

---

From EvezArt/evez-os, MIT.

More from EvezArt/evez-os