Standup Notes Command

Command

/standup

Description

Generates a standup-ready status report by analyzing your recent git commits, branch activity, open PRs, and current working state. Formats output for easy copy-paste into Slack, Teams, Jira, or standup bots.

Behavior

1. Analyze git log for commits since last standup (default: last 24 hours)
2. Check current branch and uncommitted changes
3. List open pull requests authored by you
4. Identify blockers from TODO/FIXME comments and failing tests
5. Format into a clean standup report

Data Sources

Copy
# Commits since yesterday
git log --since="yesterday" --author="$(git config user.name)" --oneline

# Current working state
git status --short
git branch --show-current

# Open PRs (if gh CLI available)
gh pr list --author @me --state open

# Recent TODOs added
git diff HEAD~5 | grep "^+.*TODO\|^+.*FIXME"

Output Format

Copy
## Standup - March 25, 2026

### Done (Yesterday)
- Implemented rate limiting middleware for API endpoints
  - `feat: add sliding window rate limiter` (abc1234)
  - `feat: add per-endpoint rate config` (def5678)
- Fixed timezone bug in scheduling service
  - `fix: use UTC for all cron calculations` (ghi9012)

### In Progress (Today)
- **Rate Limiting** [feature/rate-limiting]
  - Adding response headers (X-RateLimit-*)
  - Writing integration tests
  - PR: #234 (awaiting review)
- **Scheduling** [fix/timezone-cron]
  - PR: #231 (2 approvals, merging today)

### Blockers
- Need decision on rate limit for /search endpoint (asked in #backend)
- CI pipeline flaky on integration tests (unrelated to my changes)

### PRs
- #234: Add API rate limiting - Draft, 3 files changed
- #231: Fix timezone in cron scheduler - Ready to merge

Configuration

Customize in the command or via environment:

Copy
# Lookback period (default: 24h)
/standup --since "2 days ago"

# Output format
/standup --format slack    # Slack markdown
/standup --format jira     # Jira markup
/standup --format plain    # Plain text

# Include specific repos (monorepo)
/standup --paths backend/ shared/

Rules

1. Focus on outcomes, not tasks ("Implemented rate limiting" not "edited 5 files")
2. Group related commits under a single bullet point
3. Always include PR numbers and status when available
4. Flag blockers clearly - these are the most important part
5. Keep it concise - aim for 30-second read time

Examples

Copy
# Standard standup
/standup

# Last 3 days (after a weekend)
/standup --since "3 days ago"

# Slack-formatted output
/standup --format slack