Skip to content

commandWorkflow

Standup Summary

Summarizes what you changed since yesterday from git history and the working tree, in a form you can read out at standup.

npx workspacetemplates add standup-summary --tool claude-code

Writes 1 file to .claude/commands/

.claude/commands/standup-summary.md14 lines · 1.1 KBFile
---
description: Summarizes what you changed since yesterday from git history and the working tree, in a form you can read out at standup.
argument-hint: "[author or time range, optional]"
---

Summarize recent work for standup. Scope: $ARGUMENTS (my commits since the last working day if empty).

1. Get the author from `git config user.name`. Choose the start: yesterday, or Friday if today is Monday, unless the user gave a range.
2. Run `git log --all --author="<name>" --since="<start>" --pretty="%h %ad %s" --date=short` and `git status --short`. Check `git stash list` and the current branch.
3. Group the commits by branch or feature. Read the diff of a commit only when its subject is vague.
4. Write three parts, each two or three bullets at most: **Done** (finished and merged or pushed), **In progress** (uncommitted or unpushed work, with the branch), **Blocked or needs input** (only if the history shows reverts, long-lived drafts or failing work; otherwise write "nothing visible").
5. Do not invent plans for today. End with one line asking what to add that git cannot know.

Keep it under 120 words, in the first person, plain language.

What it does

Standup is easier when you do not have to remember Tuesday. This command reads your commits, branches and uncommitted work and turns them into three short parts: done, in progress and blocked.

It looks at your own work by default, handles weekends by going back to the last working day, and says plainly when the history is too thin to claim anything.

Example

you › /standup-summary

agent › Done: finished the retry logic for webhooks and pushed it (feature/webhook-retry, 4 commits).
In progress: tests for the backoff timer, uncommitted in 2 files.
Blocked: nothing visible.
Anything else to add, like meetings or reviews?

Questions

Can it summarize my whole team?
Yes, pass an author name or a range such as "team since Monday" and it widens the search.
Does it see work outside git?
No. Meetings, reviews and chat are not in the history, so it asks you to add them.
  • Debug Error

    CommandWorkflow

    Free
  • Estimate Task

    CommandWorkflow

    Free
  • Explain Code

    CommandWorkflow

    Free
  • Plan Feature

    CommandWorkflow

    Free