Use when the user wants a team development report generated from git history — commits, merged PRs, contributor activity, and statistics. Trigger on 'weekly report', 'what did we ship', 'sprint summary', 'contribution report', 'git activity summary', 'team contributions', 'generate report from git', 'development activity report', 'what did the team ship', 'stakeholder update from git data', 'sprint review summary', 'show commits by author', 'merged PRs this week', or any request for a data-driven summary of team development progress over a time window. Requires .devt/config.json git configuration. This is for GIT-BASED team activity reports, NOT for session summaries, NOT for Jira/ticket reports, NOT for postmortems or incident reports, NOT for code review reports, NOT for architecture health reports, and NOT for progress updates sourced from non-git data.

Weekly Report

Overview

A weekly report transforms raw git data (commits, PRs, diffs) into a human-readable summary of what the team accomplished. It answers "what did we ship?" without requiring manual tracking.

The report is generated from data, not from memory. Git is the source of truth.

The Iron Law

NO REPORT CONTENT FROM MEMORY — ALL DATA FROM GIT

LLMs naturally confabulate plausible-sounding work summaries, commit messages, and contribution details. A report generated from memory will sound professional but may attribute wrong commits to wrong people, invent PR numbers, or describe work that happened in a different week. Git data is the single source of truth — every claim in the report must trace to a real commit, PR, or diff.

Reports generated from recall are inaccurate and biased. Git commits, PRs, and diffs are the single source of truth. Fetch the data, then summarize it.

The Process

Step 1: Verify Configuration

Read .devt/config.json for git configuration:

{
  "git": {
    "provider": "bitbucket|github|gitlab",
    "workspace": "team-workspace",
    "slug": "repo-name",
    "contributors": ["user1", "user2"]
  }
}

If this configuration is missing, the report cannot be generated. Ask the user to configure .devt/config.json.

Step 2: Compute Time Window

Determine the reporting period:

Default: Last 7 days (Monday to Sunday)
Custom: User-specified date range
Sprint: Based on sprint start/end dates if configured

Step 3: Fetch Git Data

Gather from the git provider:

Commits: All commits in the window by configured contributors
Branches: Active branches with recent activity
Files changed: Aggregated file change statistics

Group commits by:

Author
Branch/feature
Type (feature, fix, refactor, docs, test)

Step 4: Fetch PR Data

Gather pull request activity:

Merged PRs: PRs merged during the window
Open PRs: PRs still in review
Review activity: Comments, approvals, change requests

Step 5: Render Report

Structure the report as:

# Weekly Report: [date range]

## Highlights

- [Top 3-5 accomplishments in plain language]

## Merged Pull Requests

| PR  | Title | Author | Files | Additions | Deletions |
| --- | ----- | ------ | ----- | --------- | --------- |

## Commits by Author

### [Author Name]

- [branch] commit message (files changed)

## In Progress

- [Open PRs and active branches]

## Statistics

- Commits: X
- PRs merged: X
- Files changed: X
- Lines added: X
- Lines removed: X

Highlights should be written in plain language for non-technical stakeholders. The rest provides detail for the team.

Gate Functions

Gate: Configuration Present

.devt/config.json has git.provider, git.workspace, git.slug
At least one contributor configured in git.contributors

Gate: Data Fetched

Commits retrieved for the time window
PR data retrieved (merged + open)
No API errors or authentication failures

Gate: Report Quality

Highlights are in plain language (not commit messages)
All merged PRs are listed
Statistics are accurate (match raw data)

Anti-patterns

Anti-pattern	Why it fails	Instead
"Nothing happened this week"	Something always happened -- you are not looking hard enough	Check all contributors and all branches
"The API is not responding"	Giving up at the first error loses the report	Verify credentials and provider configuration
"The report is too long"	Unstructured length obscures accomplishments	Summarize in highlights; keep detail in expandable sections
"I'll write the report from memory"	Memory is unreliable. Git data is not.	Generate from git data, then edit for clarity
"Only merged PRs matter"	In-progress work provides context for next week	Include open PRs and active branches
"Statistics are vanity metrics"	Trends in statistics reveal process issues	Track trends over time, not just single-week numbers
"The report is just bureaucracy"	A data-driven summary saves 30 minutes of standup updates	Let the data speak -- automate the busywork

When NOT to Use

Skip mid-sprint — reports are designed for end-of-week or end-of-sprint summaries.

Time Budget

Data collection: 1-2 minutes. Report rendering: 30 seconds.

Integration

Prerequisites: .devt/config.json configured with git provider details
CLI: devt-tools.cjs report window [--weeks N], devt-tools.cjs report generate [--weeks N] [--output PATH]
Used by agents: workflow orchestrator (can trigger at end of sprint)
Related skills: lesson-extraction (report may surface accomplishments worth recording)

weekly-report