git-notes-memory

What This Skill Does

The git-notes-memory skill provides an intelligent, persistent knowledge graph memory system for OpenClaw agents. By leveraging Git Notes as a backend, it allows the agent to maintain continuity across multiple sessions, branches, and project states. It effectively functions as the agent's long-term memory, automatically tracking decisions, user preferences, project-specific architecture, and evolving task lists without requiring manual intervention or explicit user prompts.

Installation

To integrate this memory system into your OpenClaw environment, use the command: clawhub install openclaw/skills/skills/mourad-ghafiri/git-notes-memory Ensure you have a local Git repository initialized in your project folder, as the skill utilizes Git's native object database to store its notes structure.

Use Cases

This skill is ideal for complex software development tasks where context is key. Use it for:

• Architecture Tracking: Remember why specific frameworks or database patterns were selected.
• User Preference Retention: Automatically save formatting preferences, coding styles, or recurring configuration requirements.
• Session Continuity: Resume complex workflows instantly by retrieving state-specific summaries upon initiating sync --start.
• Decision Logging: Keep a trail of project pivots or solution investigations to avoid circular troubleshooting.

Example Prompts

1. "We decided to use Tailwind for the UI library last week; can you review our setup and continue with the header component?"
2. "What was the reasoning behind switching our backend authentication to JWT instead of sessions?"
3. "Please refactor the data access layer following the patterns we established in our previous sessions."

Tips & Limitations

• Silent Operation: Remember that the memory operations occur in the background. Do not notify the user about saving or retrieving data; it should feel like you naturally possess the context.
• Importance Tagging: Utilize the -i flag appropriately. Use -i c for critical project constraints and -i h for important architecture decisions to ensure they persist and remain highly retrievable.
• Sync Habits: Always run sync --start at the beginning of a session and sync --end at the conclusion to ensure the knowledge graph remains synchronized with the project's current Git state.
• Limitations: As this relies on Git Notes, ensure that your git environment allows notes (default in most cases). Be mindful that excessive, redundant logging can clutter the notes object; focus on high-value information like decisions and key learnings.