gemini-checkpoint-management

# Gemini Checkpoint Management

## MANDATORY: Invoke gemini-cli-docs First

> **STOP - Before providing ANY response about Gemini checkpointing:**
>
> 1. **INVOKE** `gemini-cli-docs` skill
> 2. **QUERY** for the specific checkpointing topic
> 3. **BASE** responses EXCLUSIVELY on official documentation loaded

## Overview

Meta-skill for managing Gemini CLI's checkpointing system. Checkpointing creates automatic snapshots before file modifications, enabling instant rollback.

## When to Use This Skill

**Keywords:** checkpoint, rollback, restore, undo, snapshot, revert, experiment, checkpointing, /restore

**Use this skill when:**

- Enabling or configuring checkpointing
- Listing available checkpoints
- Restoring to a previous state
- Understanding checkpoint storage
- Planning experimental workflows

## How Checkpointing Works

When enabled, before any file modification Gemini creates:

1. **Git Snapshot**: Shadow repo at `~/.gemini/history/<project_hash>`
2. **Conversation History**: Complete session state
3. **Pending Tool Call**: The operation about to execute

Checkpoints are stored locally and don't interfere with your project's Git repository.

## Configuration

### Enable Checkpointing

Add to `settings.json`:

```json
{
  "general": {
    "checkpointing": {
      "enabled": true
    }
  }
}
```

### Verify Configuration

```bash
cat ~/.gemini/settings.json | jq '.general.checkpointing'
```

## Commands

### List Checkpoints

```text
/restore
```

Shows available checkpoint files for the current project.

### Restore Checkpoint

```text
/restore <checkpoint_file>
```

Restores files and conversation to the checkpoint state.

### Checkpoint Naming

Format: `{timestamp}-{filename}-{tool_name}`

Example: `2025-06-22T10-00-00_000Z-my-file.txt-write_file`

## Storage Locations

| Data | Location |
| --- | --- |
| Git snapshots | `~/.gemini/history/<project_hash>` |
| Checkpoint metadata | `~/.gemini/tmp/<project_hash>/checkpoints` |

## Keyword Registry (Delegate