Analytics

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

Data-driven insights without opening a browser. Get velocity, burndown, time tracking, and team metrics directly in your terminal.

Commands

Velocity

View sprint velocity over time:

gitscrum analytics velocity

Output:

📈 Velocity - acme-dashboard

Sprint          │ Committed │ Completed │ Velocity
────────────────┼───────────┼───────────┼──────────
Sprint 15       │    52 pts │    48 pts │      92%
Sprint 14       │    48 pts │    45 pts │      94%
Sprint 13       │    45 pts │    47 pts │     104%
Sprint 12       │    50 pts │    42 pts │      84%
Sprint 11       │    45 pts │    44 pts │      98%

Average:        47 pts/sprint
Trend:          ↗ +3% vs last 5 sprints

Chart View

gitscrum analytics velocity --chart

Sprint Velocity (last 8 sprints)

  52 │                                    ▄▄
  48 │                        ▄▄          ██  ▄▄
  45 │      ▄▄      ▄▄        ██    ▄▄    ██  ██
  42 │      ██      ██  ▄▄    ██    ██    ██  ██
  38 │      ██      ██  ██    ██    ██    ██  ██
  35 │ ▄▄   ██      ██  ██    ██    ██    ██  ██
  32 │ ██   ██  ▄▄  ██  ██    ██    ██    ██  ██
     └──────────────────────────────────────────
       S8  S9  S10 S11 S12  S13  S14  S15  S16

▄▄ Committed  ██ Completed

Date Range

gitscrum analytics velocity --last 10  # Last 10 sprints
gitscrum analytics velocity --since "2025-01-01"

Burndown

Sprint burndown chart:

gitscrum analytics burndown

Output:

🔥 Burndown - Sprint 15 (Feb 3-14)

Points │
   52  │ ●
   45  │   ╲  ●
   38  │      ╲  ●    ●
   31  │         ╲      ╲  ●
   24  │            ─────────  ●
   17  │                         ╲
   10  │                            ╲
    3  │                               ╲ (ideal)
    0  │─────────────────────────────────●
       └───────────────────────────────────
        Mon  Tue  Wed  Thu  Fri  Mon  Tue
        
● = Actual   ─ = Ideal

Status: On track (2 pts ahead of ideal)
Remaining: 18 pts | Days left: 4

Previous Sprint

gitscrum analytics burndown --sprint 14
gitscrum analytics burndown --sprint "Sprint 14"

Data Export

gitscrum analytics burndown --format csv > burndown.csv

Time Tracking Reports

Personal Time

gitscrum analytics time

Output:

⏱️  Time Report - Feb 2026

Week        │ Logged   │ Tasks │ Avg/Task
────────────┼──────────┼───────┼─────────
Feb 3-7     │  32h 15m │    12 │  2h 41m
Jan 27-31   │  38h 42m │    15 │  2h 35m
Jan 20-24   │  35h 10m │    14 │  2h 31m
Jan 13-17   │  29h 55m │    11 │  2h 43m

This month:   142h 02m
Last month:   156h 23m

Team Time

gitscrum analytics time --team

⏱️  Team Time - Feb 2026

Member          │ Logged   │ Tasks │ Efficiency
────────────────┼──────────┼───────┼───────────
@john.dev       │  42h 15m │    18 │       112%
@sarah.dev      │  38h 42m │    15 │       105%
@alex.dev       │  35h 10m │    14 │        98%
@mike.dev       │  29h 55m │    12 │        92%
@lisa.dev       │  28h 30m │    11 │        88%

Team total:      174h 32m
Team average:     34h 54m

By Project

gitscrum analytics time --project

⏱️  Time by Project - Feb 2026

Project              │ Logged   │ Tasks │ % of Total
─────────────────────┼──────────┼───────┼───────────
acme-dashboard       │  68h 15m │    28 │       39%
mobile-app           │  52h 42m │    22 │       30%
api-v2               │  35h 10m │    15 │       20%
internal-tools       │  18h 25m │     8 │       11%

By Task Type

gitscrum analytics time --by-type

⏱️  Time by Type - Feb 2026

Type         │ Logged   │ Count │ Avg
─────────────┼──────────┼───────┼────────
Feature      │  95h 30m │    32 │  2h 59m
Bug          │  42h 15m │    28 │  1h 31m
Refactor     │  22h 45m │     8 │  2h 51m
Docs         │  14h 02m │     5 │  2h 48m

Team Performance

Aggregate team metrics:

gitscrum analytics team

Output:

👥 Team Analytics - acme-dashboard

                    This Sprint │ Last Sprint │ Trend
────────────────────────────────┼─────────────┼──────
Tasks Completed            28   │         24  │  ↗ +17%
Points Delivered           48   │         42  │  ↗ +14%
Avg Cycle Time          3.2d    │       3.8d  │  ↘ -16%
Throughput             5.6/day  │      4.8/d  │  ↗ +17%
Time Logged           156h      │       148h  │  ↗ +5%

Top Performers
──────────────
🥇 @john.dev     - 48 pts completed
🥈 @sarah.dev    - 42 pts completed  
🥉 @alex.dev     - 38 pts completed

Blockers Resolved: 8
Avg Resolution: 1.2 days

Individual Stats

gitscrum analytics team --member john.dev

Project Summary

Quick project health check:

gitscrum analytics summary

Output:

📊 acme-dashboard - Summary

Sprint 15 (ends Feb 14)
───────────────────────
Progress:    ████████████░░░░░░░░ 60%
Velocity:    48/52 pts (92% projected)
Burndown:    On track (+2 pts vs ideal)

This Week
─────────
Completed:   12 tasks (28 pts)
In Progress: 8 tasks
Blocked:     2 tasks
Time Logged: 68h 42m

Highlights
──────────
• Sprint velocity trending up (+8% vs avg)
• 2 blockers unresolved >2 days
• Team capacity at 95%

Actions Needed
──────────────
⚠️  GS-445 blocked 3 days - needs attention
⚠️  GS-467 overdue by 2 days

Cycle Time

Task cycle time analysis:

gitscrum analytics cycle-time

⏳ Cycle Time - Last 30 Days

Stage           │ Avg Time │ Min    │ Max
────────────────┼──────────┼────────┼────────
Todo → Progress │    4.2h  │   15m  │  2.1d
Progress → Review │  1.2d  │   2h   │  4.8d
Review → Done   │    6.5h  │   30m  │  1.8d

Total Cycle     │    2.8d  │  0.5d  │  7.2d

By Type
───────
Feature:    3.4d avg
Bug:        1.8d avg
Hotfix:     4.2h avg
Chore:      1.2d avg

Trend

gitscrum analytics cycle-time --trend

Cycle Time Trend (12 weeks)

  5d │      ●
  4d │  ●       ●
  3d │      ●       ●   ●   ●
  2d │                      ●   ●   ●
  1d │                              ●
     └────────────────────────────────
      W1  W2  W3  W4  W5  W6  W7  W8  W9  W10 W11 W12

Trend: ↘ -32% improvement

Export Formats

JSON

gitscrum analytics velocity --format json

{
  "project": "acme-dashboard",
  "sprints": [
    {
      "name": "Sprint 15",
      "committed": 52,
      "completed": 48,
      "velocity_percent": 92
    }
  ],
  "average_velocity": 47,
  "trend": "+3%"
}

CSV

gitscrum analytics time --format csv > time_report.csv

Markdown

gitscrum analytics summary --format markdown > report.md

Scheduled Reports

Configure automated reports in .gitscrum.yml:

analytics:
  reports:
    - type: velocity
      schedule: "every friday 17:00"
      output: ./reports/velocity.json
    
    - type: time
      schedule: "end of sprint"
      output: ./reports/time.csv
    
    - type: summary
      schedule: "daily 09:00"
      notify: slack

CI/CD Integration

Generate reports in CI:

# .github/workflows/analytics.yml
name: Weekly Analytics
on:
  schedule:
    - cron: '0 17 * * 5'  # Friday 5 PM

jobs:
  report:
    runs-on: ubuntu-latest
    steps:
      - name: Generate reports
        run: |
          gitscrum analytics summary --format markdown > report.md
          gitscrum analytics velocity --format json > velocity.json
          gitscrum analytics time --format csv > time.csv
        env:
          GITSCRUM_ACCESS_TOKEN: ${{ secrets.GITSCRUM_ACCESS_TOKEN }}
      
      - name: Upload artifacts
        uses: actions/upload-artifact@v4
        with:
          name: weekly-analytics
          path: |
            report.md
            velocity.json
            time.csv

Comparison Flags

Compare against baselines:

# vs last sprint
gitscrum analytics velocity --compare last-sprint

# vs same period last month
gitscrum analytics time --compare last-month

# vs specific sprint
gitscrum analytics burndown --compare "Sprint 10"