weekly-reportlisted

# 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: ```json { "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 d