Meetings

Write Your Standup Update in 30 Seconds

Yesterday, today, blockers — drafted from your actual commits and calendar.

Tools you'll use
ClaudeGitHub
5 minEasyProduct · OperatorUpdated Jun 2026
The gist

Standup updates eat more time than they should — not the typing, the remembering. This drafts a clean "yesterday / today / blockers" straight from your GitHub activity and calendar, so you stop reconstructing your own day from memory. Paste, skim, post.

Who this is for

Anyone on a team with a daily or async standup who'd rather spend the two minutes actually working. Especially good for async written updates in Slack.

What you'll need

  • Your GitHub activity (commits, PRs, reviews) for the day — your profile's activity feed or git log both work.
  • Your calendar for what's ahead.
  • A Claude account.
The workflow

Grab your trail · 2 min

Copy yesterday's commit messages and PR titles. From the terminal, git log --since="yesterday" --oneline --author="you" is the fastest. Add a glance at today's calendar.

Draft the update · 2 min

standup prompt
Turn my raw activity into a standup update. Format:

**Yesterday:** 2–3 bullets, outcomes not tasks ("shipped X" not "worked on X").
**Today:** 2–3 bullets from my calendar + obvious follow-ups.
**Blockers:** anything stuck, or "None." Be specific about what would unblock me.

Keep it skimmable and plain — no corporate filler. If a commit message is cryptic, ask me what it was instead of guessing.

Commits/PRs:
[paste]

Calendar / plans:
[paste]

Skim and post · 1 min

Fix anything the commit messages garbled, make sure a blocker is actually a blocker, and post. That's it.

Where people trip up

Listing tasks instead of outcomes. "Worked on auth" tells nobody anything. "Shipped login, fixing the token-refresh edge case today" does.

Soft-pedaling blockers. Standup is the cheapest place to surface a blocker. If you're stuck, say exactly what would unstick you.

Trusting cryptic commits. If your commit messages are "wip" and "fix", the update will be too. Let Claude ask rather than invent.

Do this next

  1. Save it as a snippet or text-expander so the prompt is one keystroke away each morning.
  2. Write better commit messages — the cleaner the trail, the better the auto-draft. The habit pays off twice.
  3. Pipe it into your async channel with the same format every day so teammates can scan it fast.
Did this one work for you?
Help me decide what to build next

Want me to go deeper on this one?

I'm exploring in public, not productizing first — so this is a signal, not a pre-order. Tap what you'd actually want, and the most-requested ones get made.

Notes & comments 0

No notes yet — be the first to say how it went.

Keep going →

Keep going

Get the next one when it drops.

You read this to the end — the next workflow can come straight to your inbox.