Skip to Content
Cheat Sheet/log-session

/log-session

Capture a session journal — what was delivered, what blocked, what was learned — and save it to reports/session-journals/ so future sessions inherit the context this one created.

When to use it

Run this at the end of a working session, especially after a meaningful one (multiple PRs shipped, a hard bug solved, an architectural decision made, a /drain completed). The command gathers the session’s git log, PRs, board changes, and conversation context, then drafts a structured journal — tickets delivered, challenges and mitigations, insights and learnings, metrics, next moves. Save lands at reports/session-journals/YYYY-MM-DD.md (or a -N.md suffix if multiple sessions land on the same day).

The journal is the load-bearing artifact for cross-session context. Conversation context resets between sessions; the journal is what carries the “we tried this, it failed for this reason” knowledge forward. Future operators reading the journal pick up the thread without having to re-derive it.

Also: the journal’s structured-reflection step proposes Memory MCP entities for any concrete insights worth surviving the session itself — LessonLearned for gotchas, PatternDiscovered for reusable patterns. The operator confirms which ones to keep.

Don’t skip this even if “nothing happened” — the act of writing it forces the question “did anything actually happen?” If the answer is genuinely no, the journal can be one paragraph.

How it fits

The journal becomes the cross-session memory layer; Memory MCP entities capture the most reusable insights for direct agent recall.

What it does (quick)

  • Gathers session signals — git log, PRs merged/opened, board state changes, completed tickets
  • Drafts a journal with Tickets Delivered, Challenges + Mitigations, Insights + Learnings, Metrics, Next Up
  • Cross-references the draft against git log to catch anything missed
  • Proposes Memory MCP entities for concrete insights (LessonLearned, PatternDiscovered) — operator confirms before writes
  • Saves to reports/session-journals/YYYY-MM-DD.md
  • /validate-memory — natural follow-up; confirms the journal’s claimed CompletedTickets have Memory MCP entities
  • /prune-memory — paired discipline; this command adds memory, that command removes stale memory
  • /release-decision — when a session culminates in a release, the journal captures the decision rationale

Canonical spec: .claude/commands/log-session.md

Last updated on
/release-decision/prune-memory