ck

Persists per-project session context and auto-loads project briefings via Node.js scripts.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill ck-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/ck
Command: npx skills add https://github.com/ibytechaos/claude --skill ck-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Claude Code sessions start with no memory of previous work, forcing you to re-explain project goals, decisions, and progress every time. This Skill maintains persistent per-project memory so context survives across sessions. ## Core Features & Use Cases - Project Registration: Auto-detects project name, stack, goal, and constraints from package.json, Cargo.toml, go.mod, pyproject.toml, CLAUDE.md, and README.md via /ck:init. - Session Save & Resume: Records summaries, decisions, next steps, blockers, and git activity with /ck:save, then restores a full briefing with /ck:resume. - SessionStart Hook: Injects a compact ~100-token project summary at session start, detecting unsaved sessions, new git commits, and goal mismatches with CLAUDE.md. - Use Case: You work across five repositories. Run /ck:init in each, then /ck:save at the end of every session. Next time you open a project, the hook shows where you left off and what to do next. ## Quick Start Register the current project by asking the assistant to run the ck init command and confirm the auto-detected project details.

Frequently Asked Questions about ck

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

FAQPage Schema
How do I save Claude Code session context between conversations?

Run /ck:save at the end of a session. The assistant drafts a summary with left-off state, next steps, decisions, and blockers, then pipes it to a Node.js script that writes context.json and regenerates CONTEXT.md for the project.

How to auto-load project context when a Claude Code session starts?

Register the session-start.mjs hook in ~/.claude/settings.json under the SessionStart hooks array. The hook injects a compact five-line summary with goal, left-off state, next steps, and git activity, using roughly 100 tokens.

Does ck work with projects in languages other than JavaScript?

Yes. The init script detects stack and name from package.json, go.mod, Cargo.toml, and pyproject.toml, plus CLAUDE.md and README.md. The scripts themselves require Node.js but the tracked project can use any language.

Where does ck store project context data?

Data lives in ~/.claude/ck/ with a projects.json registry and per-project context.json files under contexts/. A generated CONTEXT.md view is written alongside, and session entries are also copied to Claude Code native memory.

What happens if I forgot to save a session in ck?

The SessionStart hook compares the previous session ID against saved sessions and warns that the last session was not saved, prompting you to run /ck:save. It also reports git commits made since the last recorded session.