Skip to content

Instantly share code, notes, and snippets.

@adibhanna
Last active March 12, 2026 21:45
Show Gist options
  • Select an option

  • Save adibhanna/48cdb717d70ceb0d3965ccc56ead627f to your computer and use it in GitHub Desktop.

Select an option

Save adibhanna/48cdb717d70ceb0d3965ccc56ead627f to your computer and use it in GitHub Desktop.
Claude Code /standup command — generates daily standup notes from git activity

Generate a concise standup summary and append it to a daily file.

Steps

  1. Determine today's date and the current user:

    • date +%Y-%m-%d for the date
    • git config user.name for the author name
  2. Set the standup file path: ~/standup/{date}.md

    • Create the directory if it doesn't exist
  3. Read the existing file (if any) to avoid duplicating items already listed.

  4. Find all git repos to scan:

    • Start from the current working directory and its parent
    • Find all directories containing a .git folder (search 2-3 levels deep)
    • Also check common workspace roots: parent directory, grandparent directory
  5. For each repo found, scan for today's work by the current user:

    • git log --all --oneline --since="midnight" --author="{user}" for commits
    • gh pr list --state merged --search "merged:>={date}" --limit 10 --json number,title for merged PRs
    • Run these in parallel across repos for speed
    • Skip repos with no activity
  6. Compare findings against what's already in the file. Only add NEW items not already covered.

  7. Format new items as short bullet points:

    • Keep each item to 1 line — what was done + PR/repo reference if applicable
    • Group related items (e.g. "Switched to host networking — PRs: backend#61, plc-go#1, pulse#65")
    • No deep technical details — just what and where
    • Think "5 minutes of talking time" level of detail
  8. Append new items to the file using this format:

# Standup — {date}

- Item one
- Item two
- Item three

If the file already has a header and items, only append new bullets under the existing list. Do NOT rewrite or duplicate existing items.

  1. Show the user the final file contents so they can review.

Keep it brief. This is for a 5-minute verbal update, not a detailed report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment