A Git-backed memory layer and CLI tool that provides durable, version-controlled, and auditable memory for AI coding agents without cluttering your working tree.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install git-as-memory
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install git-as-memory using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Git as Memory (git-as-memory) is a specialized utility designed to give AI coding agents a durable, version-controlled, and highly auditable memory layer. By storing memory records within a dedicated Git reference (refs/git-as-memory/memory/v1) instead of the active working tree, it ensures that project-specific decisions, user preferences, and stable context are preserved across sessions without cluttering your repository's working files.
As a core capability in the Openclaw Skills registry, this tool empowers agents like OpenClaw, Hermes, and Claude Code to read, search, and write key-value structured memories. It bridges the gap between ephemeral agent context and long-term project knowledge, ensuring your AI assistants get smarter the more they work on your codebase.
To get started, verify if the companion CLI gam is already installed on your system. It is a key tool for managing storage within Openclaw Skills integrations:
command -v gam
If the command is missing, install the CLI globally via npm or pip:
npm install -g git-as-memory
# Or alternatively
pip install git-as-memory
For one-off usage without global installations, use npx or python execution:
npx git-as-memory --help
# Or python CLI runner
python -m git_as_memory.cli --help
Initialize the Git memory reference in your project repository (this process is idempotent and safe to run multiple times):
gam init --repo /path/to/repo
Git as Memory stores all files within the standard Git object database, isolated under the dedicated ref branch refs/git-as-memory/memory/v1.
| Type | Description | Use Case Example |
|---|---|---|
| entity | User, project, or tool preference profiles | User prefers highly concise console command answers |
| semantic | Durable facts, architectural decisions, and rules | Discovered release or deployment workflow conventions |
| episodic | Compact summary of an entire session or task | Brief run-down of a migration script execution |
| working | Short-lived task context or active state files | Intermediate execution metadata destined to be pruned |
| hypothesis | Unverified inference or technical assumption | Guess on why a specific legacy API is failing under load |
Records are identified using stable kebab-case identifiers mapped directly to storage directories:
<type>/<stable-id>
Example paths generated inside the isolated Git tree:
Loading
An advanced metacognitive engine for structuring complex user requests, selecting and orchestrating subordinate AI skills, and delegating shared concerns.

An automated meta-skill designed to streamline the entire lifecycle of custom AI skill creation, local validation, security scanning, and publishing to ClawHub.

An agent-agnostic tool for converting multi-format documents, spreadsheets, audio files, and web pages into structured Markdown or HTML.

A command-line integration and AI agent capability that automates task, project, and attachment management on TickTick and Dida365.

A privacy-aware, tiered memory management component for AI agents that secures sensitive data with custom XOR+Base64 encryption and automated cleanup protocols.

A professional social media analyzer designed to evaluate, score, and optimize Xiaohongshu (RED) post content for maximum platform engagement.








































