Weekly Summaries

The week command creates detailed summaries of your work over a week, combining live git data with historical journal entries to provide a complete picture of your accomplishments.

Quick Start

Generate a summary for the current week:

devdaily week

Generate last week’s summary:

devdaily week --last

How It Works

Determine Date Range

Calculate the week boundaries (Monday to Sunday or custom range).

Gather Live Data

Analyze git commits, pull requests, and tickets from the current repository.

Enrich with Journal

Pull historical snapshots from your work journal for continuity and context.

AI Generation

Generate a comprehensive summary showing accomplishments, progress, metrics, and notable items.

Output & Save

Display the summary and optionally save it to your journal for future reference.

Command Options

Time Range Options

Option	Description
`-l, --last`	Last week instead of current week
`-s, --start <date>`	Custom start date (YYYY-MM-DD)
`--from <date>`	Start date for custom range (YYYY-MM-DD)
`--to <date>`	End date for custom range (YYYY-MM-DD)
`-w, --weeks-ago <number>`	Number of weeks ago (e.g., 2 = two weeks back)

Current Week
Last Week
Custom Range
Weeks Ago

# Current week (Monday to today)
devdaily week

# Previous week (last Monday to Sunday)
devdaily week --last

# Specific week
devdaily week --start 2024-01-15

# Custom date range
devdaily week --from 2024-01-10 --to 2024-01-17

# Two weeks ago
devdaily week --weeks-ago 2

# Three weeks ago
devdaily week --weeks-ago 3

Project Options

Option	Description
`--all-projects`	Include all tracked projects from journal
`-p, --project <id>`	Filter by specific project identifier

# Cross-project summary
devdaily week --all-projects

# Single project summary
devdaily week --project my-api

The --all-projects flag generates a cross-project summary using only journal data, perfect for reviewing work across multiple repositories.

Context Control

Option	Description
`--no-tickets`	Skip fetching closed tickets/issues
`--no-prs`	Skip fetching PR context
`--no-journal`	Skip journal data (use only live git)

# Skip external API calls
devdaily week --no-tickets --no-prs

# Only live git data (no historical journal)
devdaily week --no-journal

Output Options

Option	Description
`--no-copy`	Don’t copy to clipboard
`--save`	Save the summary to journal as an AI summary
`--json`	Output stats as JSON (no AI generation)
`--raw-context`	Output only raw context block (no AI)
`--debug`	Show full context and prompt sent to Copilot

# Save to journal for future reference
devdaily week --save

# Export stats as JSON
devdaily week --json

# Debug mode
devdaily week --debug

Journal Control

Option	Description
`--no-auto-snapshot`	Skip auto-saving a snapshot to journal

# Don't create auto-snapshot
devdaily week --no-auto-snapshot

Single-Project Mode

Default mode that analyzes the current repository with optional journal enrichment.

What Gets Analyzed

Live Git Data:

Commits from the week
Pull requests created/updated
Ticket IDs from commits and branches
Diff statistics (insertions/deletions)
Work categories (frontend, backend, etc.)
Top changed files

Journal History (if available):

Daily snapshots from the week
Notes and tags from each day
Branch activity across days
Historical context and continuity

Example Output

╭─────────────────────────────────────────────────╮
│ 📅 Week in Review (Jan 15 - Jan 21)            │
├─────────────────────────────────────────────────┤
│                                                 │
│ ## Accomplishments                              │
│ - Implemented user authentication system        │
│ - Fixed critical login redirect bug (PROJ-123)  │
│ - Refactored API error handling                 │
│                                                 │
│ ## In Progress                                  │
│ - PR #45: Add OAuth2 support (in review)        │
│ - Branch: feature/dashboard-redesign            │
│                                                 │
│ ## Key Metrics                                  │
│ - 23 commits across 5 days                      │
│ - +1,234 / -567 lines                           │
│ - 3 PRs merged, 1 in progress                   │
│                                                 │
│ ## Notable Items                                │
│ - Breaking change: Updated auth API endpoints   │
╰─────────────────────────────────────────────────╯

 commits: 23  lines added: +1234  lines removed: -567
 PRs: 3  tickets: 5  primary area: backend
 journal days: 5

Cross-Project Mode

Use --all-projects to see work across multiple repositories.

Generate a summary spanning all projects tracked in your journal:

devdaily week --all-projects

What Gets Analyzed

All journal snapshots from the week across all projects
Per-project commit counts and active days
Branch activity per project
Work category breakdown per project
Cross-cutting themes and patterns

Example Cross-Project Output

╭─────────────────────────────────────────────────╮
│ 📅 Cross-Project Week in Review (Jan 15 - 21)  │
├─────────────────────────────────────────────────┤
│                                                 │
│ ## Week Overview                                │
│ Heavy focus on backend infrastructure across    │
│ API and dashboard projects. Context switching   │
│ between bugfixes and new feature work.          │
│                                                 │
│ ## Per-Project Highlights                       │
│                                                 │
│ ### my-api (3 days, 18 commits)                 │
│ - Migrated authentication to OAuth2             │
│ - Fixed critical production bugs                │
│                                                 │
│ ### dashboard (2 days, 12 commits)              │
│ - Redesigned user settings page                 │
│ - Added real-time notifications                 │
│                                                 │
│ ## Cross-Cutting Themes                         │
│ - Auth improvements across both projects        │
│ - Testing infrastructure week                   │
╰─────────────────────────────────────────────────╯

 projects: 2  active days: 5  total commits: 30
 lines added: +2156  lines removed: -892

Per-Project Breakdown

After the summary, see detailed stats per project:

📂 Per-Project Breakdown

  my-api                          18 commits · 3 days  +1234/-456
    Branches: feature/oauth2, fix/login-bug, main
    Areas: backend(75%), tests(15%), docs(10%)

  dashboard                       12 commits · 2 days  +922/-436
    Branches: feature/settings-redesign, feature/notifications
    Areas: frontend(85%), backend(15%)

Weekly Summary Structure

The AI-generated summary includes:

Single-Project Structure

Accomplishments - Key completed work
In Progress - Active work and open PRs
Key Metrics - Commits, changes, PRs merged
Notable Items - Breaking changes, refactors, patterns

Cross-Project Structure

Week Overview - High-level themes across projects
Per-Project Highlights - Key accomplishments per project
Cross-Cutting Themes - Patterns and shared concerns
This Week in Numbers - Aggregate stats

Saving Summaries

Save to Journal

devdaily week --save

Saves the AI-generated summary to your journal for future reference and searching.

Auto-Snapshot

By default, running devdaily week creates a snapshot entry. Disable with:

devdaily week --no-auto-snapshot

Example Workflows

End-of-Week Review

# Friday afternoon - review the week
devdaily week --save

# Copy to clipboard for team update

Cross-Project Status

# Monthly review across all projects
devdaily week --all-projects --from 2024-01-01 --to 2024-01-31

Custom Range Summary

# Sprint review (2-week sprint)
devdaily week --from 2024-01-08 --to 2024-01-21

Historical Analysis

# Last month's first week
devdaily week --weeks-ago 4

# Export as JSON for analysis
devdaily week --weeks-ago 4 --json > week-data.json

Quick Last Week

# Monday morning - review last week
devdaily week --last --save

Data Sources

The weekly summary combines two data sources:

Live Git Data (Current Repo)

✅ Most accurate for current state
✅ Includes latest commits and changes
✅ Real-time PR and ticket status

Journal History (Saved Snapshots)

✅ Historical continuity across days
✅ Shows work progression
✅ Includes notes and tags
✅ Cross-project visibility

Journal entries are created with devdaily snapshot or auto-saved by other commands.

Configuration

Customize weekly summaries in .devdaily.json:

{
  "git": {
    "defaultBranch": "main"
  },
  "output": {
    "showStats": true,
    "copyToClipboard": true
  }
}

JSON Output

For automation and integrations:

devdaily week --json

Single-project JSON:

{
  "dateRange": { "from": "2024-01-15", "to": "2024-01-21" },
  "commits": 23,
  "pullRequests": 3,
  "tickets": 5,
  "diffStats": {
    "filesChanged": 42,
    "insertions": 1234,
    "deletions": 567
  },
  "categories": [
    { "name": "backend", "percentage": 75 },
    { "name": "tests", "percentage": 15 }
  ],
  "branch": "main",
  "journalEntries": 5
}

Cross-project JSON:

{
  "projects": [
    {
      "projectId": "my-api",
      "totalCommits": 18,
      "activeDays": 3,
      "branches": ["feature/oauth2", "main"],
      "diffStats": { "insertions": 1234, "deletions": 456 }
    }
  ],
  "totalCommits": 30,
  "totalActiveDays": 5
}

Troubleshooting

No data found for this week

If you see “No commits, PRs, or journal entries found”:

Verify you’re in a git repository
Check the date range is correct
Use --debug to see what’s being analyzed
Try --all-projects if you have journal entries

Cross-project mode shows nothing

You need journal snapshots for cross-project summaries:

# Start taking snapshots
devdaily snapshot

# View your journal
devdaily snapshot --list

Copilot CLI not found

Install GitHub Copilot CLI:

gh extension install github/gh-copilot

devdaily standup - Daily standup generation
devdaily snapshot - Take work snapshots
devdaily context - Recover work context
devdaily recall - Search work history

Get Started

Core Features

Configuration

Advanced

Troubleshooting

Quick Start

How It Works

Command Options

Time Range Options

Project Options

Context Control

Output Options

Journal Control

Single-Project Mode

What Gets Analyzed

Example Output

Cross-Project Mode

What Gets Analyzed

Example Cross-Project Output

Per-Project Breakdown

Weekly Summary Structure

Single-Project Structure

Cross-Project Structure

Saving Summaries

Example Workflows

End-of-Week Review

Cross-Project Status

Custom Range Summary

Historical Analysis

Quick Last Week

Data Sources

Live Git Data (Current Repo)

Journal History (Saved Snapshots)

Configuration

JSON Output

Troubleshooting

​Quick Start

​How It Works

​Command Options

​Time Range Options

​Project Options

​Context Control

​Output Options

​Journal Control

​Single-Project Mode

​What Gets Analyzed

​Example Output

​Cross-Project Mode

​What Gets Analyzed

​Example Cross-Project Output

​Per-Project Breakdown

​Weekly Summary Structure

​Single-Project Structure

​Cross-Project Structure

​Saving Summaries

​Example Workflows

​End-of-Week Review

​Cross-Project Status

​Custom Range Summary

​Historical Analysis

​Quick Last Week

​Data Sources

​Live Git Data (Current Repo)

​Journal History (Saved Snapshots)

​Configuration

​JSON Output

​Troubleshooting

​Related Commands

Quick Start

How It Works

Command Options

Time Range Options

Project Options

Context Control

Output Options

Journal Control

Single-Project Mode

What Gets Analyzed

Example Output

Cross-Project Mode

What Gets Analyzed

Example Cross-Project Output

Per-Project Breakdown

Weekly Summary Structure

Single-Project Structure

Cross-Project Structure

Saving Summaries

Example Workflows

End-of-Week Review

Cross-Project Status

Custom Range Summary

Historical Analysis

Quick Last Week

Data Sources

Live Git Data (Current Repo)

Journal History (Saved Snapshots)

Configuration

JSON Output

Troubleshooting

Related Commands