budmem - Memory System

Handle memory operations based on the command in $ARGUMENTS:

Command Routing

Parse $ARGUMENTS and execute:

Session Initialization

At session start, automatically:

1. Read MEMORY.md to load long-term context
2. Scan memory/ for files from the last 7 days
3. Keep recent learnings in context for duplicate detection

Command: (empty) - Show Status

Display memory status and recent learnings.

Steps:

1. Read MEMORY.md and summarize content
2. List files in memory/ sorted by date (newest first)
3. Show last 5 learnings from most recent files

Command: add <content>

Add a new learning to today's file.

Steps:

1. Extract content from $ARGUMENTS (everything after "add ")
2. Check for duplicates - search existing memories for similar content
3. If duplicate found, show it and ask user to confirm
4. Auto-detect metadata from content and conversation context
5. Append to memory/YYYY-MM-DD.md using entry format below
6. Confirm with one-line summary

Auto-detected metadata:

• Category: correction | pattern | preference | architecture | convention Service: budapp | budadmin | budcluster | budsim | budgateway | budmodel | budmetrics | budnotify | ask-bud | budeval | budplayground | budCustomer | general
• Tags: Extract key terms from content

Command: search <query>

Search across all memory files.

Steps:

1. Extract query from $ARGUMENTS (everything after "search ")
2. Search MEMORY.md for matches
3. Search all files in memory/ folder
4. Display matches with file location and context

Command: promote

Move learnings from daily files to MEMORY.md.

Steps:

1. List recent learnings from memory/ files (last 7 days)
2. Ask user which to promote (number or content)
3. Append to MEMORY.md under appropriate section
4. Mark as promoted in source file with [PROMOTED] tag

Command: flush

Save current session learnings before context is lost.

Steps:

1. Review conversation for corrections, preferences, patterns
2. Check each against existing memories for duplicates
3. Present list and ask user to confirm each
4. Write confirmed learnings to today's file
5. Suggest any that should be promoted to MEMORY.md

Command: clean

Archive daily files older than 30 days.

Steps:

1. Create memory/archive/ if needed
2. Move files older than 30 days to archive
3. Report: "Archived X files from [date range]"

Entry Format

markdown
1## [HH:MM] Title
2
3**Category**: correction | pattern | preference | architecture | convention
4**Service**: budapp | budadmin | budcluster | budsim | budgateway | general
5**Tags**: tag1, tag2
6
7> The learning content in one or two sentences.
8
9---

Auto-Learn Triggers

Detect these patterns in user messages and offer to save:

Hooks (Optional)

Add to .claude/settings.json for automatic reminders:

json
1{
2  "hooks": {
3    "PreCompact": [
4      {
5        "matcher": "auto",
6        "hooks": [
7          {
8            "type": "command",
9            "command": "echo 'BUDMEM: Context compacting. Run /budmem flush to save learnings.'"
10          }
11        ]
12      }
13    ]
14  }
15}

File Structure

.claude/skills/budmem/
├── SKILL.md              # This file
├── MEMORY.md             # Long-term curated knowledge
└── memory/
    ├── YYYY-MM-DD.md     # Daily logs
    └── archive/          # Old files (30+ days)

MEMORY.md Sections

markdown
1# Long-term Memory
2
3## Architecture Decisions
4## Coding Preferences
5## Project Conventions
6## Service-Specific
7### budapp
8### budadmin
9### budcluster
10### budsim
11### budgateway
12### budmodel
13### budmetrics
14### budnotify
15### ask-bud
16### budeval
17### budplayground
18### budCustomer
19### general
20## Anti-patterns

Examples

Add a learning:

/budmem add Always use structlog for logging in Python services
> Checking duplicates... none found.
> Added to memory/2025-02-04.md (category: convention, service: general)

Search:

/budmem search logging
> Found 2 matches:
> - memory/2025-02-04.md: "Always use structlog for logging..."
> - MEMORY.md: "All services use structlog with JSON output"

Duplicate detection:

/budmem add Use structlog for logging
> Similar learning exists in memory/2025-02-04.md:
> "Always use structlog for logging in Python services"
> Still add? (y/n)