remember

Summarize the current work session and persist metadata via memory-db.sh.

15|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/iagocavalcante/claude-turbo-search --skill remember-iagocavalcante
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/iagocavalcante/claude-turbo-search/tree/main/skills/remember
Command: npx skills add https://github.com/iagocavalcante/claude-turbo-search --skill remember-iagocavalcante

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain continuity across work sessions by persisting a summarized record of what was accomplished, which files were touched, and learnings for future prompts.

Core Features & Use Cases

  • Session summarization: Generates a concise recap of the current activity.
  • Progress tracking: Logs modified or touched files for traceability.
  • Cross-session memory: Stores key insights and learnings for retrieval in future conversations.

Quick Start

Run the /remember command to summarize the session and persist it to memory for future context.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I save my work session context for future reference?

To save your work session context, run the /remember command to summarize activity, track modified files, and persist metadata via memory-db.sh for cross-session continuity.

What is cross-session memory persistence in software engineering?

Cross-session memory persistence stores summarized records of accomplished work, modified files, and key learnings to maintain context across future work sessions.

How do I track modified files and log activity across coding sessions?

You track modified files and log activity by running a script-driven workflow that reads the activity log, generates a concise summary, and persists the metadata.

Does the session summarization workflow require external dependencies?

The session summarization workflow requires no external dependencies, using an internal script-driven approach to read activity logs and persist data via memory-db.sh.

Why do I lose context and learnings when starting a new work session?

You lose context and learnings because session data is volatile, but you can prevent this by persisting a summarized record of insights and modified files to memory.