mirror of
https://github.com/affaan-m/ECC.git
synced 2026-09-18 07:37:59 +02:00
d29cf651c7
* fix(skills): move version into metadata and normalize to semver 29 skills declared `version` at the top level of their frontmatter. The schema reads it from `metadata`, so tooling that follows the schema either misses it or has to special-case the top level. Three motion skills also declared `version: 1.0`, which is not a valid semantic version; normalized to `1.0.0`. No behavioral change — frontmatter metadata only. * fix(skills): state activation triggers in skill descriptions 148 skills described what they cover but never named the situation that should trigger them. Since the description is what Claude matches against to decide whether to load a skill, a description without a trigger makes activation guesswork — the skill is either missed or loaded at the wrong time. Added a "Use when ..." clause to each, derived from the skill's own body (most already stated the trigger under "## When to Use" or in the opening line; that intent is now reflected in the frontmatter where it is actually read from). Descriptions were only appended to; no existing wording was removed. * fix(skills): sync activation triggers into the Codex skill mirror 10 of the skills whose descriptions changed are also mirrored under `.agents/skills/`, where the description was previously a verbatim copy. Left alone, the two surfaces would disagree about when the skill applies. Only the description line is synced; the Codex copies keep their reduced frontmatter, since that validator accepts only name, description, metadata, license, and allowed-tools. * fix(skills): correct three activation clauses from review - autonomous-loops: the clause pulled new loop work into a skill that its own body marks as a compatibility shim retained for one release. It now points at the canonical continuous-agent-loop instead. - continuous-learning: the description carried the v1 routing directive twice; collapsed to one. - homelab-pihole-dns: the clause fired on any broken home DNS. Narrowed to tasks that actually involve Pi-hole. * chore: retain current main lockfile --------- Co-authored-by: Çağrı Solakoğlu <cagri.solakoglu@vtcenerji.com> Co-authored-by: haelyra <49814733+haelyra@users.noreply.github.com>
149 lines
4.8 KiB
Markdown
149 lines
4.8 KiB
Markdown
---
|
|
name: ck
|
|
description: Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions. Use when a project needs context to survive across Claude Code sessions instead of being re-explained each time.
|
|
metadata:
|
|
version: 2.0.0
|
|
origin: community
|
|
author: sreedhargs89
|
|
repo: https://github.com/sreedhargs89/context-keeper
|
|
---
|
|
|
|
# ck — Context Keeper
|
|
|
|
You are the **Context Keeper** assistant. When the user invokes any `/ck:*` command,
|
|
run the corresponding Node.js script and present its stdout to the user verbatim.
|
|
Scripts live at: `~/.claude/skills/ck/commands/` (expand `~` with `$HOME`).
|
|
|
|
---
|
|
|
|
## Data Layout
|
|
|
|
```
|
|
~/.claude/ck/
|
|
├── projects.json ← path → {name, contextDir, lastUpdated}
|
|
└── contexts/<name>/
|
|
├── context.json ← SOURCE OF TRUTH (structured JSON, v2)
|
|
└── CONTEXT.md ← generated view — do not hand-edit
|
|
```
|
|
|
|
---
|
|
|
|
## Commands
|
|
|
|
### `/ck:init` — Register a Project
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/init.mjs"
|
|
```
|
|
The script outputs JSON with auto-detected info. Present it as a confirmation draft:
|
|
```
|
|
Here's what I found — confirm or edit anything:
|
|
Project: <name>
|
|
Description: <description>
|
|
Stack: <stack>
|
|
Goal: <goal>
|
|
Do-nots: <constraints or "None">
|
|
Repo: <repo or "none">
|
|
```
|
|
Wait for user approval. Apply any edits. Then pipe confirmed JSON to save.mjs --init:
|
|
```bash
|
|
echo '<confirmed-json>' | node "$HOME/.claude/skills/ck/commands/save.mjs" --init
|
|
```
|
|
Confirmed JSON schema: `{"name":"...","path":"...","description":"...","stack":["..."],"goal":"...","constraints":["..."],"repo":"..." }`
|
|
|
|
---
|
|
|
|
### `/ck:save` — Save Session State
|
|
**This is the only command requiring LLM analysis.** Analyze the current conversation:
|
|
- `summary`: one sentence, max 10 words, what was accomplished
|
|
- `leftOff`: what was actively being worked on (specific file/feature/bug)
|
|
- `nextSteps`: ordered array of concrete next steps
|
|
- `decisions`: array of `{what, why}` for decisions made this session
|
|
- `blockers`: array of current blockers (empty array if none)
|
|
- `goal`: updated goal string **only if it changed this session**, else omit
|
|
|
|
Show a draft summary to the user: `"Session: '<summary>' — save this? (yes / edit)"`
|
|
Wait for confirmation. Then pipe to save.mjs:
|
|
```bash
|
|
echo '<json>' | node "$HOME/.claude/skills/ck/commands/save.mjs"
|
|
```
|
|
JSON schema (exact): `{"summary":"...","leftOff":"...","nextSteps":["..."],"decisions":[{"what":"...","why":"..."}],"blockers":["..."]}`
|
|
Display the script's stdout confirmation verbatim.
|
|
|
|
---
|
|
|
|
### `/ck:resume [name|number]` — Full Briefing
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/resume.mjs" [arg]
|
|
```
|
|
Display output verbatim. Then ask: "Continue from here? Or has anything changed?"
|
|
If user reports changes → run `/ck:save` immediately.
|
|
|
|
---
|
|
|
|
### `/ck:info [name|number]` — Quick Snapshot
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/info.mjs" [arg]
|
|
```
|
|
Display output verbatim. No follow-up question.
|
|
|
|
---
|
|
|
|
### `/ck:list` — Portfolio View
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/list.mjs"
|
|
```
|
|
Display output verbatim. If user replies with a number or name → run `/ck:resume`.
|
|
|
|
---
|
|
|
|
### `/ck:forget [name|number]` — Remove a Project
|
|
First resolve the project name (run `/ck:list` if needed).
|
|
Ask: `"This will permanently delete context for '<name>'. Are you sure? (yes/no)"`
|
|
If yes:
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/forget.mjs" [name]
|
|
```
|
|
Display confirmation verbatim.
|
|
|
|
---
|
|
|
|
### `/ck:migrate` — Convert v1 Data to v2
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/migrate.mjs"
|
|
```
|
|
For a dry run first:
|
|
```bash
|
|
node "$HOME/.claude/skills/ck/commands/migrate.mjs" --dry-run
|
|
```
|
|
Display output verbatim. Migrates all v1 CONTEXT.md + meta.json files to v2 context.json.
|
|
Originals are backed up as `meta.json.v1-backup` — nothing is deleted.
|
|
|
|
---
|
|
|
|
## SessionStart Hook
|
|
|
|
The hook at `~/.claude/skills/ck/hooks/session-start.mjs` must be registered in
|
|
`~/.claude/settings.json` to auto-load project context on session start:
|
|
|
|
```json
|
|
{
|
|
"hooks": {
|
|
"SessionStart": [
|
|
{ "hooks": [{ "type": "command", "command": "node \"~/.claude/skills/ck/hooks/session-start.mjs\"" }] }
|
|
]
|
|
}
|
|
}
|
|
```
|
|
|
|
The hook injects ~100 tokens per session (compact 5-line summary). It also detects
|
|
unsaved sessions, git activity since last save, and goal mismatches vs CLAUDE.md.
|
|
|
|
---
|
|
|
|
## Rules
|
|
- Always expand `~` as `$HOME` in Bash calls.
|
|
- Commands are case-insensitive: `/CK:SAVE`, `/ck:save`, `/Ck:Save` all work.
|
|
- If a script exits with code 1, display its stdout as an error message.
|
|
- Never edit `context.json` or `CONTEXT.md` directly — always use the scripts.
|
|
- If `projects.json` is malformed, tell the user and offer to reset it to `{}`.
|