Claude Session Kit

claude-session-kit

Mine your Claude Code sessions for patterns. Back up every session, summarize each one with an LLM, then cross-reference across sessions to surface recurring friction, missing skills, codebase smells, documentation gaps, and test coverage holes — every finding cites the real sessions it came from.

[](https://www.npmjs.com/package/claude-session-kit) [](https://github.com/penspanic/claude-session-kit/actions/workflows/ci.yml) [](./LICENSE)

flowchart LR
  jsonl["~/.claude/projects/
*.jsonl
deleted after 30d"]

  subgraph csk["claude-session-kit"]
    direction TB
    backup["csk backup"] --> store[("SQLite index
+ blob mirror
+ FTS5 search")]
    store --> analyze["csk analyze
per-session LLM summary
intent · friction · corrections"]
    analyze --> patterns["csk patterns
project / global
cross-session findings"]
  end

  jsonl --> backup

  findings["Findings
• repetition / skill_gap
• correction_pattern
• codebase_smell / api_friction
• documentation_gap / test_coverage_gap

→ CLAUDE.md · new skill · refactor · docs · tests"]
  patterns --> findings

  surfaces["CLI  |  Web dashboard (csk serve)  |  MCP server (agents)"]
  store --- surfaces
  findings --- surfaces

Why

Your Claude Code sessions are the highest-signal record of how you *actually* work with an AI — every correction you made, every time the assistant got stuck on the same thing, every recurring intent. But:

1. They disappear. Claude Code deletes sessions after 30 days by default (cleanupPeriodDays).
2. One session tells you what happened that time. The interesting signal — "I keep redirecting the assistant away f