apappascsapappascs/claude-code-sessions/skills/session-timeline/SKILL.md

session-timeline

Skill2 starsChanged 26 days agoMITView on GitHub

Shows a chronological timeline of all Claude Code sessions for a project. Use when the user asks "what's the history of this project", "show me all sessions", "session timeline", or wants to see patterns in their work.

1 other project uses a version of this.

Adopted by

Most recently taken up by

microsoft/vscode-team-kittheir own version, first seen Nov 1, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
microsoft/vscode-team-kit★ 65same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- session-cleanupSkill
- session-deleteSkill
- session-detailSkill
- session-diffSkill
- session-exportSkill
- session-listSkill
- session-memory-auditSkill
- session-memory-searchSkill
- session-memorySkill
- session-resumeSkill
- session-searchSkill
- session-statsSkill
- session-tasksSkill

The file

Create a free account to mount

Files

SKILL.md

Session Timeline

Show chronological history of sessions for a project.

Step 1: Run the timeline script

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts timeline --project "$(basename $(pwd))" --format json

To show only recent sessions:

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts timeline --project "$(basename $(pwd))" --since "2026-04-01" --format json

Step 2: Present the timeline

The script outputs a JSON array of sessions in chronological order (each entry has a title: custom title if set, else auto title; may be null). Present as a visual timeline:

2026-04-08  ████░░░░  45m  main        (12 messages)
2026-04-09  ██████░░  1h 20m  feat/cli  (34 messages)
2026-04-10  ██░░░░░░  15m  feat/cli    (8 messages)
2026-04-11  ████████  2h 10m  main      (56 messages)

Identify patterns:

Daily cadence or sporadic?
Long sessions vs short?
Branch switches?
Gaps in activity?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free