claude-code/commands/summarize.md

name, description, aliases

name	description	aliases
summarize	Summarize and save the current session context	save-session session-summary

/summarize Command

Summarize the current session and save key information to memory.

When Invoked

Extract and save important information from the current conversation:

1. Decisions made → memory/decisions.json
2. Preferences learned → memory/preferences.json
3. Project context → memory/projects.json
4. Facts discovered → memory/facts.json

Process

Step 1: Analyze Session

Review the conversation for:

• Explicit decisions ("let's use X", "we decided Y")
• Implicit preferences ("I prefer", "always do X")
• Project-related context (paths, configs, conventions)
• Facts about the environment or user

Step 2: Categorize Items

For each item, determine:

• Category: decision, preference, project, fact
• Content: Brief description
• Context: Why it matters (optional)

Step 3: Save to Memory

Append to the appropriate memory file:

{
  "id": "uuid",
  "date": "YYYY-MM-DD",
  "content": "Description of item",
  "context": "Additional context",
  "session": "session-id"
}

Step 4: Update History Index

Mark session as summarized in history/index.json:

{
  "sessions": [
    {
      "id": "session-id",
      "started": "timestamp",
      "summarized": true
    }
  ]
}

Output Format

📝 Session Summary

Saved to memory:
• Decision: Use plugin structure for .claude config
• Preference: Prefer scripts over inline code in skills
• Fact: Gmail venv at ~/.claude/mcp/gmail/venv

Session marked as summarized.

Memory File Locations

File	Content
~/.claude/state/personal-assistant/memory/decisions.json	Choices made
~/.claude/state/personal-assistant/memory/preferences.json	User preferences
~/.claude/state/personal-assistant/memory/projects.json	Project context
~/.claude/state/personal-assistant/memory/facts.json	Environment facts

When to Use

• End of a productive session
• After making important decisions
• When asked to "remember this"
• Before long breaks

Policy

• Only save genuinely useful information
• Avoid redundancy with existing memory
• Keep descriptions concise
• Include context when helpful