session-diff
Skill2 starsChanged 26 days agoMITView on GitHub
Compares two Claude Code sessions — shows what changed in files, tools used, branches, and topics. Use when the user says "what changed between sessions", "diff sessions", "compare yesterday and today", or wants to understand how work evolved across sessions.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- session-cleanupSkill
- session-deleteSkill
- session-detailSkill
- session-exportSkill
- session-listSkill
- session-memory-auditSkill
- session-memory-searchSkill
- session-memorySkill
- session-resumeSkill
- session-searchSkill
- session-statsSkill
- session-tasksSkill
- session-timelineSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If the user provides two session IDs, resolve them:
- Very specific: line 21
Use the path fields from the results.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Session Diff
Compare two sessions to see what changed.
Step 1: Resolve session paths
If the user provides two session IDs, resolve them:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts list --project "$(basename $(pwd))" --limit 2 --format jsonUse the path fields from the results.
Step 2: Run the diff
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts diff <session-a.jsonl> <session-b.jsonl>Step 3: Interpret and present
The script outputs raw structural data. Your job is to synthesize the narrative:
- What was the focus of each session? (use
first_user_messages) - Files added/dropped/common between sessions
- Branch changes (did they switch branches?)
- Tool usage shifts (more editing? more reading? more testing?)
- Continuity — does session B pick up where A left off?
Present as a side-by-side comparison with your interpretation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.