# Work Summary > Generate a summary of work done based on git commit history across one or more repositories. Use for standups, timesheets, retrospectives, or any time you need a structured overview of what was accomplished in a time period. - Skill: `supatest-ai/work-summary` (Agent Skill) - Install (CLI): `npx skillmds@latest add supatest-ai/work-summary` - Raw SKILL.md: https://api.skillmd.com/api/skills/supatest-ai/work-summary/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: supatest-ai (https://skillmd.com/u/supatest-ai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/supatest-ai/work-summary --- # Work Summary Generator Generate a summary of work done based on git commit history. ## Arguments ` [repo2] [repo3]...` ### Examples - `/work-summary Alice "2026-01-08 09:00" "2026-01-09 18:00" frontend backend` - `/work-summary "Alice Smith" "2026-01-07 09:00" "2026-01-07 18:00" .` ## When to use this skill Use this skill when you need to: - Generate work summaries for standup or status reports - Create summaries for timesheets or billing - Review what was accomplished in a time period - Prepare for retrospectives or reviews - Track work across multiple repositories ## Instructions ### 1. Parse Arguments If no arguments provided, ask the user for: 1. **Author name** - Git author to filter by 2. **Start date/time** - Format: `YYYY-MM-DD HH:MM` (in local timezone) 3. **End date/time** - Format: `YYYY-MM-DD HH:MM` (in local timezone) 4. **Repository paths** - Space-separated, relative to current directory or absolute paths Example prompts: ``` Please provide: - Author name: (e.g., "Alice" or "Alice Smith") - Start time: (e.g., "2026-01-08 09:00") - End time: (e.g., "2026-01-08 18:00") - Repositories: (e.g., "frontend backend" or "." for current) ``` ### 2. Collect Git Data For each repository: **Get commits:** ```bash cd && git log --author="" --since="" --until="" --pretty=format:"%h|%s" ``` **Get stats:** ```bash cd && git log --author="" --since="" --until="" --shortstat --pretty=format:"%h" ``` **Notes:** - Assume the user's local timezone unless otherwise specified - Handle relative paths (convert to absolute if needed) - If repo doesn't exist, warn and skip it ### 3. Group and Categorize Commits **Group related commits** into logical tasks: - Same feature across multiple commits - Related bug fixes - Single refactoring effort - Use commit message prefixes to help (feat, fix, refactor, chore, docs, test) **Categorize by size:** **Large Tasks:** - New packages or major modules - Significant new functionality with multiple components - Major architectural changes - Complex features spanning many files - Examples: "Add authentication system", "Implement payment processing" **Medium Tasks:** - Feature additions to existing modules - Substantial refactoring efforts - Multi-file changes with moderate complexity - API endpoint additions - Examples: "Add user profile editing", "Refactor API error handling" **Small Tasks:** - Bug fixes - UI tweaks and styling - Single-file changes - Cleanup and formatting - Documentation updates - Minor refactors - Examples: "Fix typo", "Update button color", "Add JSDoc" ### 4. Calculate Totals - Total commit count across all repos - Total lines added (sum from git stats) - Total lines deleted (sum from git stats) - Total distinct tasks ### 5. Generate HTML Output Create a self-contained HTML report at `/tmp/work-summary.html`: ```html Work Summary: <start> - <end>

Work Summary: -

Author:

NCommits

~XkLines added

~YkLines deleted

NTasks

Large Tasks (N)

Task Name (repo) — Brief description

Medium Tasks (N)

Task Name (repo) — Brief description

Small Tasks (N)

Fix login validation error (repo)

``` Save the file and report the path to the user. ## Examples ### Example 1: With Arguments ``` User: "/work-summary Alice '2026-02-13 09:00' '2026-02-13 18:00' frontend" You: 1. cd frontend 2. Run git log commands 3. Analyze commits 4. Generate HTML report at /tmp/work-summary.html Summary: 15 commits, ~2k lines added, ~500 lines deleted across 8 distinct tasks ``` ### Example 2: Multiple Repos ``` User: "/work-summary 'Alice Smith' '2026-02-01 00:00' '2026-02-07 23:59' frontend backend docs" You analyze commits across all three repos, group by task, and generate /tmp/work-summary.html. Summary: 42 commits, ~5k lines added, ~2k lines deleted across 13 distinct tasks ``` ### Example 3: No Arguments - Interactive ``` User: "/work-summary" You: "Please provide the following information: - Author name: (e.g., 'Alice' or 'Alice Smith') - Start date/time: (format: YYYY-MM-DD HH:MM, e.g., '2026-02-13 09:00') - End date/time: (format: YYYY-MM-DD HH:MM, e.g., '2026-02-13 18:00') - Repository paths: (space-separated, e.g., 'frontend backend' or '.' for current directory)" User: "Alice, 2026-02-13 09:00, 2026-02-13 18:00, ." You: [Process current directory as repository and generate summary] ``` ## Tips - **Smart grouping**: Combine commits like "Add feature X", "Fix feature X bug", "Update feature X tests" into one task - **Use commit messages**: Look for conventional commit prefixes (feat:, fix:, refactor:, etc.) - **Context matters**: A 10-line change to a critical file might be "Medium", while a 100-line new test file might be "Small" - **Repo names**: Only show repo names if analyzing multiple repos - **Time zones**: Default to local timezone but respect user's timezone if specified - **Clarity**: Make task descriptions clear and business-value focused - **Accuracy**: Count lines accurately from git stats ## Notes - This skill works best with clean, descriptive commit messages - For very large time ranges, consider summarizing by day or week - If no commits found, clearly state that and verify the author name and date range - Handle errors gracefully (missing repos, invalid dates, git errors)