Git-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.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Git-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.
GitNotesMemory - Claude Integration Guide
CRITICAL: SILENT OPERATION RULES
These rules are ABSOLUTE and must NEVER be violated:
NEVER ask "should I remember?" or "want me to save?"
NEVER announce "I'll remember this" or "saving to memory"
NEVER show memory command output to users
NEVER mention memory system unless user explicitly asks about it
JUST DO IT - silently in the background
Quick Reference
# Replace $SKILL_PATH with actual path to memory.py# Replace $DIR with the project directory path
python3 $SKILL_PATH/memory.py -p $DIR <command>
Essential Commands
Command
When to Use
sync --start
ALWAYS at session start
sync --end '{"summary":"..."}'
At session end (optional but recommended)
remember '{"..."}' -t tags -i h
Store important information
get <topic>
Retrieve context about a topic
search "<query>"
Full-text search across all memories
recall -i <id>
Get full details of a specific memory
Importance Flags
Flag
Level
When to Use
-i c
Critical
User says "always remember", "never forget", explicit preferences
-i h
High
Decisions, architecture choices, user corrections, preferences
-i n
Normal
General information (default)
-i l
Low
Temporary notes, might be pruned
Session Lifecycle
1. Session Start (MANDATORY)
Always run sync --start at the beginning of every session:
python3 $SKILL_PATH/memory.py -p $DIRsync --start
Output explains:
{"b":"main",// Current git branch"t":{"api":5,"auth":3},// Top topics with memory counts"c":[...],// Critical memories (always review these)"n":42,// Total memory count"h":[...]// High-importance recent memories}
Use this context to:
Understand what the user has been working on
Reference previous decisions
Maintain continuity across sessions
2. During Session
Silently remember when user:
Makes a decision: "Let's use PostgreSQL" → remember with -i h
States a preference: "I prefer tabs over spaces" → remember with -i h or -i c
Learns something: "Oh, so that's how async works" → remember with -i n
Sets a task: "We need to fix the login bug" → remember with -i n
Shares important context: Project requirements, constraints, goals
Retrieve context when:
User asks about something previously discussed → get <topic>
You need to recall a specific decision → search "<keywords>"
User references "what we decided" → check relevant memories
# Get full memory by ID
python3 $SKILL_PATH/memory.py -p $DIR recall -i abc123
# Get memories by tag
python3 $SKILL_PATH/memory.py -p $DIR recall -t architecture
# Get last N memories
python3 $SKILL_PATH/memory.py -p $DIR recall --last 5
# Overview of all memories
python3 $SKILL_PATH/memory.py -p $DIR recall
New branches automatically inherit from main/master
After git merge, run merge-branch to combine memories
Branch Workflow
1. User on main branch → memories stored in refs/notes/mem-main
2. User creates feature branch → auto-inherits main's memories
3. User works on feature → new memories stored in refs/notes/mem-feature-xxx
4. After git merge → run merge-branch to combine memories
Memory Types (Auto-Detected)
The system automatically classifies memories based on content:
Type
Trigger Words
decision
decided, chose, picked, selected, opted, going with
Key terms: Meaningful words (common words filtered out)
What to Remember
DO remember:
User decisions and their rationale
Stated preferences (coding style, communication style, tools)
Project architecture and constraints
Important context that affects future work
Tasks, blockers, and progress
Corrections ("actually, I meant..." → high importance)
Explicit requests to remember something → critical importance
DON'T remember:
Trivial conversation
Information easily derivable from code
Secrets, passwords, API keys
One-time questions with no future relevance
Duplicate information already stored
Output Format Reference
Tier 0: sync --start
{"b":"feature-auth",// Current branch"t":{"auth":5,"api":3,"db":2},// Topics with counts"c":[{"id":"x","s":"summary","t":"preference"}],// Critical"n":15,// Total count"h":[{"id":"y","s":"summary"}]// High importance}
User: "Let's build a REST API with Python"
Claude: [silently: remember '{"decision": "REST API", "language": "Python"}' -t architecture -i h]
[responds about REST API setup WITHOUT mentioning memory]
User: "I prefer FastAPI over Flask"
Claude: [silently: remember '{"preference": "FastAPI over Flask", "reason": "user preference"}' -i h]
[continues discussion using FastAPI WITHOUT saying "I'll remember"]
User: "What did we decide about the API?"
Claude: [silently: get api]
[uses retrieved context to answer accurately]
User: "Actually, let's use Flask instead"
Claude: [silently: remember '{"decision": "Changed to Flask", "previous": "FastAPI"}' -i h]
[silently: evolve <fastapi-memory-id> "User changed preference to Flask"]
[acknowledges change WITHOUT mentioning memory update]
Troubleshooting
Memory not found:
Use search with different keywords
Check entities to see what's indexed
Use recall --last 10 to see recent memories
Context seems stale:
Always run sync --start at session beginning
Check current branch with branches
After git operations:
After git merge: run merge-branch <source-branch>
After git checkout: sync --start will load correct branch context
