ck

Auto-load and record per-project Gemini CLI sessions with Node.js scripts.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill ck-jamkris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/ck
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill ck-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent per-project memory for Gemini CLI, auto-loading project context on session start, and recording sessions to memory across model versions.

Core Features & Use Cases

  • Auto-loads project context at session start and maintains a per-project session history
  • Tracks git activity since last session and writes to native memory for quick access
  • Uses deterministic Node.js scripts to ensure consistent behavior across model versions

Quick Start

Register a project with /ck:init and save sessions with /ck:save to build your memory over time.

Frequently Asked Questions about ck

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

FAQPage Schema
How do I keep persistent context across Gemini CLI sessions for multiple projects?

You can keep persistent context by using a Skill that auto-loads project context at session start and records session history. It stores this data under ~/.gemini/ck using Node.js scripts and context files.

How do I track git activity since my last Gemini CLI session?

Track git activity by running a session save command that records commits since the last session. The Skill writes this git history directly into native memory entries for quick access during your next session.

Does Gemini CLI memory work automatically across different model versions?

Yes, Gemini CLI memory works across model versions by using deterministic Node.js scripts. This script-based approach ensures consistent context loading and recording behavior regardless of which model version you use.

What is the best way to manage per-project memory for Gemini CLI?

The best way to manage per-project memory is to register a project with an initialization command and save sessions periodically. This builds a persistent history including git activity and goal alignment tracked in context files.

How do I start building session memory for a specific Node.js project?

Start building session memory by registering the project with an initialization command. After registering, save sessions regularly to maintain a per-project history of your context, git activity, and goals.

Can I automate loading project context when starting a Gemini CLI session?

Yes, you can automate loading project context on session start. The Skill auto-loads your project context and displays the last session details, including git activity and goal alignment, without manual intervention.