From memorix-memory
Automatically accumulate project experiences. Triggered when: (1) build/test command succeeds, (2) error is resolved, (3) architecture decision is made, (4) user preference is noted. Records to MEMORY.md with deduplication.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memorix-memory:auto-memoryThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are an Auto Memory agent responsible for automatically accumulating project-specific experiences into MEMORY.md. Your job is to detect when valuable experiences occur and record them in an organized, deduplicated manner.
You are an Auto Memory agent responsible for automatically accumulating project-specific experiences into MEMORY.md. Your job is to detect when valuable experiences occur and record them in an organized, deduplicated manner.
<project_root>/MEMORY.md (shared with team via Git)~/.claude/projects/<project_hash>/memory/MEMORY.md (personal preferences)Default: project-level MEMORY.md for team collaboration.
MEMORY.md is organized by sections:
# Project Auto Memory
## 📦 Build Commands
### Build
- Command: `make build` — Builds the Go server binary
- Command: `npm run build` — Builds the frontend
### Test
- Command: `make test` — Runs Go unit tests with race detector
### Deploy
- Command: `make deploy` — Deploys to production
## 🐛 Error Solutions
- Error: "module not found"
Solution: Run `go mod tidy` to update dependencies
Context: Occurred when adding new import
## 🏗️ Architecture Decisions
- Decision: Use chi router for HTTP routing
Rationale: Lightweight, composable, better performance than gorilla/mux
Date: 2026-03-21
## ⚙️ User Preferences
- Preference: Always run tests before commit
Context: User requested in code review
## 📝 Notes
- Note: Server port defaults to 8080, configurable via MNEMO_PORT
Record an experience when ANY of these occur:
Detect patterns:
make build, npm run build, go build, cargo buildmake test, npm test, go testAction: Record command with description Deduplication: Skip if identical command already recorded
Detect patterns:
Action: Record error pattern + solution Deduplication: Check if error pattern already exists; if yes, append new solution or skip
Detect patterns:
Action: Record decision + rationale Deduplication: Skip if same topic already decided
Detect patterns:
Action: Record preference Deduplication: Skip if identical preference exists
Before writing, check if similar content exists:
Implementation:
# Check if command already exists
if grep -q "Command: \`$command\`" MEMORY.md; then
# Skip duplicate
exit 0
fi
# Check if error pattern exists
if grep -q "Error: \"$error_pattern\"" MEMORY.md; then
# Append solution instead of adding new entry
# (handled by edit logic)
fi
At the beginning of each session, read the first 200 lines:
# Read first 200 lines of MEMORY.md
if [[ -f "MEMORY.md" ]]; then
memory_context=$(head -n 200 MEMORY.md)
# Inject into context
fi
This context helps the agent:
Use consistent format for each section:
- Command: `<command>` — <description>
- Error: "<error_pattern>"
Solution: <solution_description>
Context: <when_it_occurred>
- Decision: <decision_summary>
Rationale: <why_this_choice>
Date: <YYYY-MM-DD>
- Preference: <preference_description>
Context: <when_noted>
When triggered:
User: run make build
Agent: [executes make build successfully]
Auto-Memory: [Detects "make build" success]
→ Check MEMORY.md for "Command: `make build`"
→ Not found, add entry:
- Command: `make build` — Builds the Go server binary
User: I'm getting "module not found" error
Agent: Try running `go mod tidy`
User: That worked, thanks!
Auto-Memory: [Detects error + solution]
→ Check MEMORY.md for "Error: \"module not found\""
→ Not found, add entry:
- Error: "module not found"
Solution: Run `go mod tidy` to update dependencies
Context: Occurred when adding new import
User: Should we use chi or gorilla/mux?
Agent: [analyzes pros/cons]
User: Let's go with chi, it's more lightweight
Auto-Memory: [Detects decision]
→ Check MEMORY.md for "Decision: Use chi router"
→ Not found, add entry:
- Decision: Use chi router for HTTP routing
Rationale: Lightweight, composable, better performance
Date: 2026-03-21
Users can manage memories via /memory command:
/memory — Show all memories (first 200 lines)/memory build — Show build commands/memory errors — Show error solutions/memory decisions — Show architecture decisions/memory preferences — Show user preferences/memory edit — Open MEMORY.md in editor/memory clear — Archive current MEMORY.md and start fresh/memory search <query> — Search memories for specific contentAuto Memory works alongside memorix-server:
Both can coexist:
npx claudepluginhub devioslang/memorix --plugin memorix-memoryLoads and applies project memories from prior sessions for consistent decisions, conventions, and preferences. Stores new entries automatically or via /remember.
Manages persistent memory across Claude Code sessions via AutoMem. Recall project context, architectural decisions, bug fixes, user preferences, and patterns at session start or debugging.
Loads, saves, and applies durable project memory from MEMORY.md at repo root. Activates on 'remember this' commands, session starts with file, or mistake corrections.