session-memory

Record session logs, decisions, and patterns to .claude/memory/ files.

3.0k|300|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/Chachamaru127/claude-code-harness --skill session-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-memory
Source: https://github.com/Chachamaru127/claude-code-harness/tree/main/skills/session-memory
Command: npx skills add https://github.com/Chachamaru127/claude-code-harness --skill session-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the "what was I doing?" problem by automatically recording session logs, technical decisions, and learned patterns, providing perfect context continuity every time you resume work.

Core Features & Use Cases

  • Cross-Session Memory Persistence: Automatically logs tasks, generated files, and key decisions to .claude/memory/ files at the end of each session.
  • Structured Knowledge Base: Maintains SSOT (Single Source of Truth) files like decisions.md and patterns.md for important project knowledge.
  • Use Case: Returning to a project after a week? This Skill loads the previous session's summary, reminds you of unfinished tasks (cc:WIP), and surfaces key architectural decisions, so you can immediately say "continue from last time" and be productive.

Quick Start

Say "what did we do last time?" to get a concise summary of the previous session's activities and pending tasks.

Frequently Asked Questions about session-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain context and continuity across Claude sessions?

Session memory automatically records your tasks, decisions, and learned patterns to `.claude/memory/` files, letting you resume work with full context. Say "what did we do last time?" to retrieve your previous session's summary and pending tasks.

What gets stored when I use session memory for a project?

Session memory preserves session logs, technical decisions, and learned patterns in structured files: `session-log.md` tracks activities, `decisions.md` documents key choices, `patterns.md` captures recurring approaches, and `context.json` stores metadata for quick retrieval.

Can I review what I accomplished in my last session?

Yes. Session memory logs all tasks and generated files automatically, then surfaces them as a concise summary when you return. Unfinished work is tagged as `cc:WIP` so you know exactly where to pick up.

How does session memory help when I come back to a project after time away?

It eliminates context switching by loading your previous session's summary, unfinished tasks, and architectural decisions immediately. You can resume productivity right away without re-reading old notes or reconstructing what you were doing.

Where does session memory store its data?

All memory data is stored locally in `.claude/memory/` with tagged, indexed files for sessions, decisions, and patterns. This setup enforces privacy while maintaining a single source of truth for project knowledge.