HELLO, CREATORSGood work starts with a great skill.Find yours

Claude-Mem Project Timeline Report

thedotmack/claude-mem

Turn a project’s Claude-Mem timeline into a narrative report of its development, decisions, and debugging history.

Latest update at:

101,278Stars8,870ForksRepository last pushed

About this Skill

Turn a project’s Claude-Mem timeline into a narrative report of its development, decisions, and debugging history.

Why we picked it

A reusable workflow from the Claude-Mem project. It is listed separately to explain this task; shared runtime and helper dependencies remain part of the upstream installation. The inherited gallery demonstrates the memory system, not this task’s specific output.

What it helps with

  • Explain how a project evolved across many coding sessions.

How the workflow runs

  1. Step 1

    Resolve the actual project name, including worktree-to-parent mapping.

  2. Step 2

    Retrieve the timeline and check whether the history fits the analysis context.

  3. Step 3

    Analyze major phases and supporting observations, then save the report.

Original timeline-report instructions

Expected result

A source-backed narrative report of the project’s development history.

Original timeline-report instructions

Try a concrete request

  1. Example request

    After installing the required integration, ask your agent:

    Write a project journey report covering the major decisions and debugging turning points in our memory history.

Before you use it

  • A running local Claude-Mem worker, recorded project observations, SQLite access for token metrics, and a host supporting delegated analysis.
  • Use the original upstream files and follow the documented host integration. Model or third-party service usage can carry separate costs.

Supported agents

Claude CodeCodex CLI

Sources & references

Original sources are linked below. Practical starting points are editorial suggestions from SkillHey.