context-manager

Save structured session summaries and recover matching project context.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill context-manager-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-manager
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/context-manager
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill context-manager-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from losing important progress, decisions, and context when switching between conversations or restarting work, by providing a lightweight way to persist and retrieve session state.

Core Features & Use Cases

  • Session saving with a structured summary: Captures goals, completed work, key decisions, changed files, invoked agents, open items, and a context snapshot into ~/.claude/sessions/.
  • Context recovery from project history or HANDOFF.md: Restores the most relevant prior session for the current project, or uses HANDOFF.md if present in the working directory.
  • Topic search across sessions and observations: Finds past sessions and, optionally, related tool observations using index-based, timeline, or full-detail search modes.

Use case: You pause a complex refactor, later return to the same project, and want the exact goal, decisions, open items, and relevant surrounding context without rereading everything.

Quick Start

Tell the AI to run context-manager save for your current project session so it writes a complete summary to your sessions directory.

Frequently Asked Questions about context-manager

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

FAQPage Schema
How do I save and recover Claude Code session context after restarting work?

You preserve session context by instructing the AI to run a save command that writes structured summaries—including goals, decisions, and changed files—to ~/.claude/sessions/, enabling later conversational recovery.

How does keyword search across past project history sessions work?

Keyword search works by querying an append-only index.md, timeline context, and full-detail scans to locate past discussions and related tool observations across saved developer sessions.

What is the best way to resume a complex refactor after an interruption without rereading everything?

The best way to resume a refactor is to recover session context via HANDOFF.md, which restores the exact goal, key decisions, open items, and relevant context snapshot so you can continue immediately.

Do I need a specific directory structure to maintain conversational memory for my development workflow?

You need a sessions directory at ~/.claude/sessions/ to store summaries and maintain an append-only index.md, while optionally placing a HANDOFF.md in your working directory for prioritized recovery.

Can I find related tool observations from earlier discussions when recovering a prior session?

Yes, you can find related tool observations when recovering a prior session by using the tool's multi-layer search modes, which scan the index, timeline context, and full session details for matching keywords.