Claude Code /standup command — generates daily standup notes from git activity

standup.md

Generate a standup summary and append it to a daily file. This serves two purposes: a quick verbal standup reference AND a personal work log.

Steps

1. Determine today's date: date +%Y-%m-%d

2. Set the standup file path: /Users/adibhanna/Developer/standup/{date}.md

   • Create the directory if it doesn't exist: mkdir -p /Users/adibhanna/Developer/standup

3. Read the existing file (if any) to avoid duplicating items already listed.

4. Scan for today's work across all repos in /Users/adibhanna/Developer/bonjoy/pulse-all/:

   • For each subdirectory that has a .git folder, run:
     • git log --all --oneline --since="midnight" --author="$(git config user.name)"
     • gh pr list --state merged --search "merged:>=$(date +%Y-%m-%d)" --limit 10 --json number,title
   • Run these in parallel across repos for speed.

5. Compare findings against what's already in the file. Only add NEW items not already covered.

6. Format the standup using the structure below. Group related items and deduplicate across repos.

7. Append new items to the file using this format:

# Standup — {date}

## Summary
One sentence: the throughline of the day's work. What was the main focus?

### New Features
- **Short description** — PR ref
  - Sub-detail if needed
  - *Why:* one sentence on reasoning/benefit (only for significant items)

### Improvements
- ...

### Bug Fixes / Security
- ...

### Ops / Deployment
- ...

### Docs
- ...

### PRs — ({count})
- [repo#number: title](full GitHub URL)
- ...

Formatting rules

• Only include category sections that have items — skip empty sections.
• Each item: 1-2 lines max. Bold the headline, PR ref inline.
• Group related work into a single item (e.g. fixing image refs across 3 repos = one bullet).
• Add a "Why:" line only for significant items where the reasoning or benefit isn't obvious from the description. Skip it for routine work.
• The Summary section is always required — one sentence that captures the day's theme.
• Keep it scannable. This needs to work as a 5-minute verbal reference AND hold up as a written log when read weeks later.
• The PRs section is always included at the end. Include the total PR count in the heading: ### PRs — ({count}). List every PR from the day with full GitHub URL and title. Use gh pr list JSON output to get the repo owner/name for building URLs. Format: [repo#number: title](https://github.com/owner/repo/pull/number).

If the file already has content, merge new items into the existing sections (or create new sections as needed). Do NOT rewrite or reorder existing items.

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