memory-reflect · basicmachines-co — Claude Code skill: consolidate agent memory

What memory-reflect does

Think of memory-reflect as sleep for your agent. It opens notes from the last couple of days, checks active tasks, and decides what deserves to stick around: decisions that shape future work, lessons from mistakes, working-style preferences, details about people. Weather checks and routine steps get dropped.

It then updates MEMORY.md in place, following whatever structure the file already has. New sections get added, outdated entries get rewritten instead of duplicated. Today's daily note gets a short reflection log listing what was reviewed, what moved into long-term memory and what was cleaned up. The daily notes themselves stay put — they are the raw record.

The author suggests scheduling it once or twice a day through cron or heartbeat. Another good moment is right after context compaction, when part of the history is gone. The skill leans on the recent_activity, read_note and search_notes tools, so with no note store configured it has nothing to read. While gathering material it also looks for filesystem trouble: recursive nesting like memory/memory/memory/, orphaned files, bloated notes. Those are the usual reason a reflection run ends up hoarding junk.