What does this skill do?

The Context Keeper Skill provides persistent, project-structured memory for Claude Code. It saves and retrieves the state of development sessions, decisions made, roadblocks, and next steps, ensuring complete continuity between sessions. It automatically injects a context summary when you log in and tracks Git activity since the last save.

Restore context on startup
Start a session in an existing project and immediately pick up where you left off, including your decisions and next steps.
Save Session State
Keep a structured summary of your progress, roadblocks, and decisions before closing or switching tasks.
Portfolio Management
List all your registered projects and get a quick overview of each one's status with /ck:list and /ck:info.
Migration from the Old Format
Migrate old context data (v1) to the new structured format (v2) using /ck:migrate, including simulation mode.

Usage examples

🔄 Start a project
Initialize this project with /ck:init and let me know what information you've detected to confirm.
💾 Stay logged in
Save the current session's state with /ck:save before closing it. It summarizes what we've done and the next steps.
📋 Restore context
Restore the full context of the mi-api project with /ck:resume mi-api to pick up where you left off.
🗂️ List projects
List all my projects registered with /ck:list and give me a quick overview of my portfolio.

Features

Automatic Context Loading A login hook injects a compact summary of ~100 tokens into each new session, detecting unsaved sessions and discrepancies with CLAUDE.md.
Git Activity Tracking It automatically detects Git activity since the last save to keep the context in sync with the repository.
JSON-formatted state Save summaries, checkpoints, next steps, decisions, and roadblocks in a deterministic, validated JSON format.
Slash commands /ck:* It includes init, save, resume, info, list, forget, and migrate to manage the entire context lifecycle.
Migration with Simulation The /ck:migrate command supports the --dry-run option to simulate the migration of legacy data before running it.

Frequently asked questions

Yes. The commands run Node.js scripts (.mjs) located in ~/.claude/skills/ck/commands/. You need Node.js installed on your system.
No. You must always use the provided scripts to ensure data integrity. Manual editing may corrupt the project's state.
It automatically injects a concise summary of approximately 100 tokens into each new session, detecting unsaved sessions, Git activity, and discrepancies with CLAUDE.md.
Use /ck:forget [name|number]. The skill will ask for confirmation before safely deleting the context.
Context Keeper — Persistent memory per project for Claude Code

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.