cd /news/developer-tools/a-tldr-command-for-claude-code-revie… Β· home β€Ί topics β€Ί developer-tools β€Ί article
[ARTICLE Β· art-41382] src=gist.github.com β†— pub= topic=developer-tools verified=true sentiment=Β· neutral

A /tldr command for Claude Code: review and summarize session work as clean Markdown. Great for parallel/multi-session workflows.

An engineer introduced a /tldr command for Claude Code that reviews and summarizes session work as clean Markdown, designed for parallel and multi-session workflows. The command uses git log, git status, and git diff to ground the summary in recent commits and working tree changes, while relying on conversation context for intent and outstanding items. It outputs structured Markdown with sections for overview, tickets, commits, decisions, and manual tasks, omitting empty sections.

read1 min views1 publishedJun 26, 2026
description Summarize the work performed during the current session
allowed-tools Read, Bash(git log:), Bash(git status:), Bash(git diff:*)
  • Recent commits: ! git log --oneline -30

  • Working tree status: ! git status --short

Review the work performed during the current session and summarize it for the user in Markdown, using the structure below.

Scope "the current session" to work done in this conversation. Use the git context above to ground the Commits section; rely on the conversation for intent, tickets, and outstanding items. Omit any section with no relevant content β€” no empty headings, no "N/A" placeholders.

Broad-strokes bullets covering the most important work done this session. Omit technical detail unless it is critical or poses a risk to the system once deployed.

Tickets and epics created for this project during the session, shown in hierarchical order: each epic on its own line with its child stories nested beneath it. Render as a tree, using β”œβ”€

for each child and └─

for the last child under an epic. List standalone tickets (no parent epic) at the top level with no prefix. Wrap the whole block in a fenced code block so the tree alignment is preserved. For example:

EPIC-123 β€” Build the resume scoring pipeline
  β”œβ”€ STORY-456 β€” Implement the ATS parser
  β”œβ”€ STORY-457 β€” Define the scoring rubric
  └─ STORY-458 β€” Wire up the JSON output schema

EPIC-124 β€” Investor summary refresh
  └─ STORY-461 β€” Tighten unit-economics assumptions

TASK-999 β€” One-off cleanup with no parent epic

Commits made during this session, each as <short-sha> β€” <subject>

.

Decisions still needed from the user.

Manual tasks the user must perform, in the order they should be done.

── more in #developer-tools 4 stories Β· sorted by recency
── more on @claude code 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain β€” perfect for shipping the agent you just read about.

$git push zahid main
β†’ Live at https://your-agent.zahid.host βœ“
Get free account β†’ Pricing
from €0/mo Β· no card required
LIVE [news/a-tldr-command-for-c…] indexed:0 read:1min 2026-06-26 Β· β€”