vibegit
starsforks
How to install vibegit?
memovai/memov/vibegit
$npx -y skills add memovai/memov --skill vibegitAI-assisted version control using Memov. Track every AI interaction with your codebase.
SKILL.md
| 1 | # VibeGit - AI Coding History |
| 2 | |
| 3 | AI-assisted version control using Memov. Track every AI interaction with your codebase. |
| 4 | |
| 5 | ## Prerequisites |
| 6 | |
| 7 | This skill requires the `memov` Python package which provides the `mem` CLI command. |
| 8 | |
| 9 | ### Installation Options |
| 10 | |
| 11 | Choose one of the following methods: |
| 12 | |
| 13 | ```bash |
| 14 | # Option 1: Official install script (recommended) |
| 15 | curl -fsSL https://raw.githubusercontent.com/memovai/memov/main/install.sh | bash |
| 16 | ``` |
| 17 | |
| 18 | ### Verify Installation |
| 19 | |
| 20 | ```bash |
| 21 | mem |
| 22 | ``` |
| 23 | |
| 24 | ### Initialize in Your Project |
| 25 | |
| 26 | ```bash |
| 27 | cd your-project |
| 28 | mem init |
| 29 | ``` |
| 30 | |
| 31 | ## How to Use |
| 32 | |
| 33 | There are two ways to use VibeGit: |
| 34 | |
| 35 | 1. **Skill scripts (this folder)**: run `./scripts/*.sh` to call the local `mem` CLI. |
| 36 | 2. **MCP tools (Claude Code)**: use the MCP server tools like `mcp__mem-mcp__snap`. |
| 37 | |
| 38 | They are related but not identical: |
| 39 | |
| 40 | - Skill scripts are a thin wrapper over `mem` CLI. |
| 41 | - MCP tools may add extra behavior (e.g. auto-track untracked files, auto-sync for RAG features). |
| 42 | |
| 43 | ## Commands |
| 44 | |
| 45 | All commands should be run from the skill directory using the scripts provided. |
| 46 | |
| 47 | ### Core Operations |
| 48 | |
| 49 | | Script | Description | Usage | |
| 50 | |--------|-------------|-------| |
| 51 | | `init.sh` | Initialize memov in a project | `./scripts/init.sh` | |
| 52 | | `track.sh` | Track new files | `./scripts/track.sh file1.py file2.py -p "..." -r "..."` | |
| 53 | | `snap.sh` | Record a code change | `./scripts/snap.sh --files "file1.py,file2.py" -p "What was asked" -r "What was done"` | |
| 54 | | `history.sh` | View AI coding history | `./scripts/history.sh [--limit 20]` | |
| 55 | | `show.sh` | Show commit details | `./scripts/show.sh <commit_hash>` | |
| 56 | | `status.sh` | Check working directory status | `./scripts/status.sh` | |
| 57 | |
| 58 | ### Navigation |
| 59 | |
| 60 | | Script | Description | Usage | |
| 61 | |--------|-------------|-------| |
| 62 | | `jump.sh` | Jump to a specific snapshot | `./scripts/jump.sh <commit_hash>` | |
| 63 | | `branch.sh` | List/create/delete branches | `./scripts/branch.sh [name] [--delete name]` | |
| 64 | | `switch.sh` | Switch branches | `./scripts/switch.sh <branch_name>` | |
| 65 | |
| 66 | ### Web UI |
| 67 | |
| 68 | Before running `mem ui start`, confirm where you want to open the UI: |
| 69 | |
| 70 | - Which project directory should the UI read from? |
| 71 | - If not sure, run `pwd` and use `--loc <that path>`. |
| 72 | |
| 73 | Suggested confirmation prompt: |
| 74 | |
| 75 | | Script | Description | Usage | |
| 76 | |--------|-------------|-------| |
| 77 | | `ui_start.sh` | Start visual history browser | `./scripts/ui_start.sh [--loc /path] [--port 38888] [--foreground]` | |
| 78 | | `ui_stop.sh` | Stop the web server | `./scripts/ui_stop.sh [--loc /path]` | |
| 79 | | `ui_status.sh` | Check server status | `./scripts/ui_status.sh [--loc /path]` | |
| 80 | |
| 81 | ## Automatic Recording |
| 82 | |
| 83 | After every AI coding session, record the interaction: |
| 84 | |
| 85 | ```bash |
| 86 | ./scripts/snap.sh \ |
| 87 | --files "api.py,tests/test_api.py" \ |
| 88 | --prompt "Add authentication endpoint" \ |
| 89 | --response "Added /login POST endpoint with JWT token generation" |
| 90 | ``` |
| 91 | |
| 92 | ### Parameters |
| 93 | |
| 94 | - `--files`: Comma-separated list of files that were modified |
| 95 | - `--prompt` or `-p`: The user's original request |
| 96 | - `--response` or `-r`: Summary of what was done |
| 97 | - `--by-user` or `-u`: Mark as human edit (vs AI) |
| 98 | |
| 99 | ## RAG Features (Optional) |
| 100 | |
| 101 | Some features (semantic search, validate, vibe_debug/vibe_search tools) require installing extra dependencies. |
| 102 | |
| 103 | - CLI: install with `pip install memov[rag]` then run `mem sync` once. |
| 104 | - MCP: those tools may not appear unless RAG dependencies are installed. |
| 105 | |
| 106 | ## Examples |
| 107 | |
| 108 | ### Record a bug fix |
| 109 | |
| 110 | ```bash |
| 111 | ./scripts/snap.sh \ |
| 112 | --files "auth.py" \ |
| 113 | --prompt "Fix null pointer in login" \ |
| 114 | --response "Added null check for user object at L45" |
| 115 | ``` |
| 116 | |
| 117 | ### View recent history |
| 118 | |
| 119 | ```bash |
| 120 | ./scripts/history.sh --limit 10 |
| 121 | ``` |
| 122 | |
| 123 | ### Jump to previous state |
| 124 | |
| 125 | ```bash |
| 126 | ./scripts/jump.sh a1b2c3d |
| 127 | ``` |
| 128 | |
| 129 | ## Direct CLI Usage |
| 130 | |
| 131 | You can also use the `mem` CLI directly: |
| 132 | |
| 133 | ```bash |
| 134 | # Initialize |
| 135 | mem init |
| 136 | |
| 137 | # Track new files |
| 138 | mem track file1.py file2.py -p "Initial tracking" |
| 139 | |
| 140 | # Snapshot changes |
| 141 | mem snap --files file1.py -p "Added feature X" -r "Implemented..." |
| 142 | |
| 143 | # View history |
| 144 | mem history |
| 145 | |
| 146 | # Show specific commit |
| 147 | mem show a1b2c3d |
| 148 | |
| 149 | # Jump to snapshot |
| 150 | mem jump a1b2c3d |
| 151 | ``` |
| 152 | |
| 153 | ## What Gets Recorded |
| 154 | |
| 155 | Each snapshot captures: |
| 156 | - **Prompt**: What you asked the AI to do |
| 157 | - **Response**: What the AI said it did |
| 158 | - **Files**: Which files were changed |
| 159 | - **Diff**: Actual code changes |
| 160 | - **Timestamp**: When it happened |
| 161 | - **Source**: AI or human |
| 162 | |
| 163 | ## Benefits |
| 164 | |
| 165 | - **Never lose context**: Every AI interaction is recorded |
| 166 | - **Time travel**: Jump to any point in your coding history |
| 167 | - **Understand changes**: See not just what changed, but why |
| 168 | |
| 169 | ## Troubleshooting |
| 170 | |
| 171 | ### "memov CLI not found" error |
| 172 | |
| 173 | If you see this error when running any script, memov is not installed. Run: |
| 174 | |
| 175 | ```bash |
| 176 | # Quick check |
| 177 | ./install.sh |
| 178 | |
| 179 | # Or install manually |
| 180 | pip install memov |
| 181 | ``` |
| 182 | |
| 183 | ### Scripts not executable |
| 184 | |
| 185 | ```bash |
| 186 | chmod +x scripts/*.sh install.sh |
| 187 | ``` |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
