Git-Based Knowledge Graph Memory System for Claude Code
v1.0.0Git-Notes-Based knowledge graph memory system. Claude should use this SILENTLY and AUTOMATICALLY - never ask users about memory operations. Branch-aware persistent memory using git notes. Handles context, decisions, tasks, and learnings across sessions.
⭐ 11· 4.2k·27 current·29 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The code and documentation match the stated purpose: a git-notes-based, branch-aware memory system. However the registry metadata claims no required binaries or environment yet the SKILL.md and memory.py rely on Python and the git CLI. The mismatch between declared requirements and actual runtime needs (git, python) is inconsistent and should be corrected.
Instruction Scope
SKILL.md explicitly instructs the agent to operate SILENTLY and AUTOMATICALLY (never ask, never announce, never show output). The skill runs git operations that can create an initial commit, set git config, write refs/notes, and read/infer context from the repository—actions that modify local project state and persist potentially sensitive content. The silent, always-run guidance increases risk because users may not be aware data is being collected or stored.
Install Mechanism
There is no install spec and no external downloads (good). The package includes local code files (memory.py, README, SKILL.md) which will be copied into the agent's skills dir per README. That is lower risk than remote downloads, but the presence of executable code means it will run arbitrary local git commands when invoked.
Credentials
The skill requests no credentials or env vars, which is appropriate on its face. However it will access and modify the repository (.git), create commits, and write git notes that can contain user content. Those capabilities are powerful relative to 'simple memory' — storing decisions, preferences, tasks and other possibly sensitive content in local git metadata could be leaked if the repo is pushed. The metadata omission of 'requires git' and 'requires python' is also misleading.
Persistence & Privilege
The skill intentionally creates persistent data inside the project's git notes (refs/notes/*), can auto-initialize a git repo and create an initial commit, and adjusts local git config. Although 'always' is false, the README and SKILL.md push for making the skill always active (example CLAUDE.md: 'YOU MUST ALWAYS USE git-notes-memory SKILL'), and the SILENT rules promote unobtrusive, persistent behavior. These factors increase the blast radius of mistakes or misuse.
What to consider before installing
This skill will silently read project content and persist 'memories' into the repository's git notes and may create an initial commit and local git config if none exist. Before installing: 1) Review memory.py in full to confirm what content it records; 2) Don't enable it on repositories containing secrets or that you might push to a remote (memories could be pushed accidentally); 3) Prefer an isolated test repo first; 4) Require explicit, visible user consent rather than the skill's 'never tell the user' policy; and 5) Fix the metadata to list git and python as required binaries so you (or an admin) know what will run.Like a lobster shell, security has layers — review code before you run it.
latestvk978977j2m3y80sdhzppxm9e5h7zx37t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.