Standup

⚠️ BETA — GitScrum CLI is in active development. Open source under the MIT license. Available on GitHub.

Daily standups from your terminal. No context switching, no browser tabs.

Commands

Create Standup

Log your daily standup:

gitscrum standup new

Interactive mode prompts for standard standup format:

? What did you complete yesterday?
> Finished OAuth integration, reviewed PR #142

? What will you work on today?
> Start payment gateway integration, GS-456

? Any blockers?
> Waiting for design specs for checkout flow

✓ Standup submitted for Feb 7, 2026

One-Liner Mode

Skip prompts with flags:

gitscrum standup new \
  --done "Finished OAuth integration" \
  --doing "Payment gateway" \
  --blockers "Design specs pending"

From File

Use a file for longer updates:

gitscrum standup new --file standup.md

File format:

## Done
- Finished OAuth integration
- Reviewed PR #142

## Doing
- Payment gateway integration (GS-456)
- API documentation

## Blockers
- Waiting for design specs

View Standups

Your Standup

gitscrum standup view

Output:

📅 Standup - Feb 7, 2026

✅ Done:
   • Finished OAuth integration
   • Reviewed PR #142

🔄 Doing:
   • Payment gateway integration (GS-456)
   • API documentation

🚧 Blockers:
   • Waiting for design specs

Specific Date

gitscrum standup view --date 2026-02-05
gitscrum standup view --date yesterday
gitscrum standup view --date "last monday"

Team Standups

View your team's standups for today:

gitscrum standup team

Output:

📋 Team Standups - Feb 7, 2026

┌─────────────────────────────────────────────────────────────┐
│ @john.dev                                            9:15 AM│
├─────────────────────────────────────────────────────────────┤
│ ✅ Finished OAuth integration                               │
│ 🔄 Payment gateway (GS-456)                                 │
│ 🚧 Waiting for design specs                                 │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ @sarah.dev                                           9:32 AM│
├─────────────────────────────────────────────────────────────┤
│ ✅ Completed user dashboard, Fixed mobile layout            │
│ 🔄 Starting analytics integration                           │
│ 🚧 None                                                     │
└─────────────────────────────────────────────────────────────┘

2 of 5 team members submitted (missing: alex, mike, lisa)

Filter by Team

gitscrum standup team --team backend
gitscrum standup team --team "Product Design"

Compact View

gitscrum standup team --compact

Output:

@john.dev   ✅ OAuth integration → 🔄 Payment gateway → 🚧 Design specs
@sarah.dev  ✅ Dashboard, Mobile → 🔄 Analytics → 🚧 None

Standup History

View past standups:

gitscrum standup history

Output:

📅 Your Standups

Feb 7, 2026  ✅ OAuth integration | 🔄 Payment gateway
Feb 6, 2026  ✅ Auth refactor     | 🔄 OAuth integration
Feb 5, 2026  ✅ Bug fixes         | 🔄 Auth planning
Feb 4, 2026  ✅ Sprint planning   | 🔄 Bug fixes
Feb 3, 2026  ✅ Code review       | 🔄 Sprint planning

Filter by Date Range

gitscrum standup history --since "last monday"
gitscrum standup history --since 2026-02-01 --until 2026-02-07

Export History

gitscrum standup history --format json > standups.json
gitscrum standup history --format csv > standups.csv

Edit Standup

Update today's standup:

gitscrum standup edit

Opens in your $EDITOR (vim, nano, code, etc.):

export EDITOR=code  # Use VS Code
gitscrum standup edit

Or update specific fields:

gitscrum standup edit --blockers "None - specs received"
gitscrum standup edit --doing "Payment gateway, checkout UI"

Delete Standup

Remove today's standup:

gitscrum standup delete

Delete specific date:

gitscrum standup delete --date 2026-02-05

Standup Reminders

Configure daily reminders in .gitscrum.yml:

standup:
  reminder:
    enabled: true
    time: "09:00"
    days: ["monday", "tuesday", "wednesday", "thursday", "friday"]

The CLI will remind you when you run any command after the reminder time:

⏰ Reminder: You haven't submitted today's standup yet
   Run: gitscrum standup new

Blockers Management

View All Blockers

See active blockers across the team:

gitscrum standup blockers

Output:

🚧 Active Blockers

@john.dev   - Waiting for design specs (2 days)
            → Related: GS-456 Payment Gateway

@alex.dev   - API rate limit issues with Stripe (1 day)
            → Related: GS-489 Checkout Flow

@mike.dev   - Staging environment down (3 days)
            → No related task

Resolve Blocker

Link resolved blockers:

gitscrum standup resolve-blocker "Design specs received"

Async Standups

For remote teams across timezones:

standup:
  async: true
  window_hours: 24  # Standups valid for 24h
  timezone: "UTC"

Team members can submit standups at their local morning, visible to others for 24 hours.

Standup Templates

Create custom standup templates:

standup:
  template:
    - question: "What did you ship?"
      key: done
      emoji: "🚀"
    - question: "What's in progress?"
      key: doing
      emoji: "⚡"
    - question: "Any blockers or risks?"
      key: blockers
      emoji: "⚠️"
    - question: "How's your energy level? (1-5)"
      key: energy
      emoji: "🔋"

JSON Output

For scripts and integrations:

gitscrum standup view --format json

{
  "date": "2026-02-07",
  "user": "john.dev",
  "submitted_at": "2026-02-07T09:15:00Z",
  "done": [
    "Finished OAuth integration",
    "Reviewed PR #142"
  ],
  "doing": [
    "Payment gateway integration (GS-456)"
  ],
  "blockers": [
    "Waiting for design specs"
  ]
}

CI/CD Integration

Post automated standups from CI:

# .github/workflows/standup.yml
name: Auto Standup
on:
  schedule:
    - cron: '0 9 * * 1-5'  # 9 AM weekdays

jobs:
  standup:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Generate standup from commits
        run: |
          YESTERDAY=$(date -d "yesterday" +%Y-%m-%d)
          COMMITS=$(git log --since="$YESTERDAY" --oneline)
          gitscrum standup new \
            --done "$COMMITS" \
            --doing "CI/CD automated entry" \
            --user ci-bot
        env:
          GITSCRUM_ACCESS_TOKEN: ${{ secrets.GITSCRUM_ACCESS_TOKEN }}

Best Practices

1. Be specific. "Worked on feature" → "Implemented OAuth token refresh (GS-123)"
2. Link tasks. Reference task IDs for context
3. Action blockers. Include who can help or what's needed
4. Keep it brief. Standups are status updates, not reports
5. Submit on time. Async standups have windows for a reason