Generate comprehensive daily and weekly work summaries using Claude Code. Aggregates data from your tools -- git, JIRA, Google Calendar, Slack, Google Drive, and your task manager -- into a clean markdown summary.

All data sources are optional. Enable only the ones you use. The summary adapts automatically.

cd ~/.claude/skills
git clone https://github.com/willfanguy/work-summary-kit.git

Open Claude Code and run:

/summary-init

The wizard walks you through setup. At minimum, you'll point it at your git repo(s).

/daily-summary

Your summary is written to ~/work-summaries/daily/ (configurable).

A markdown file covering your work day:

• Executive Summary -- 3-5 bullet overview
• Metrics -- Commits, tasks, meetings, focus time
• Code Activity -- Commits grouped by feature/ticket
• JIRA Updates -- Ticket status and progress
• Meetings -- Schedule, time allocation, focus quality
• Slack Activity -- Key discussions and decisions
• Drive Activity -- File modifications (metadata only)
• Completed Tasks -- From your task system
• Tomorrow's Focus -- Priority items for tomorrow
• Blockers -- Active blockers and resolution plans

Run /weekly-summary on Fridays to get:

• Week-at-a-glance metrics
• Major accomplishments (synthesized, not repeated)
• Velocity trends (week-over-week comparison)
• Project health indicators
• Key decisions and outcomes
• Next week priorities

Pick one (or none):

Choose a template that matches your role:

• daily-default -- Full detailed summary (all sections)
• daily-compact -- Quick snapshot (summary + metrics + blockers)
• daily-engineering -- Code-heavy, meetings-light
• daily-manager -- Meetings/decisions-heavy, code-light

Set your template in ~/.config/work-summary/config.json:

{
  "output": {
    "template": "daily-compact"
  }
}

Control which sections appear and in what order:

{
  "output": {
    "sections_order": [
      "executive_summary",
      "code_activity",
      "jira_updates",
      "blockers"
    ]
  }
}

Remove a section name to hide it entirely.

Map folder names to friendly display names:

{
  "project_mappings": {
    "backend-svc": "Backend Platform",
    "fe-app": "Customer Portal"
  }
}

Override display names for colleagues:

{
  "name_mappings": {
    "confirmed": {
      "[email protected]": "Bob Smith"
    }
  }
}

Run summaries on a schedule. See scheduling/README.md for:

• macOS: launchd plist templates
• Linux: cron entries
• Timeout wrapper: Prevents hung processes from blocking future runs

Full config lives at ~/.config/work-summary/config.json. See config/config.example.json for a fully annotated example.

Generated by /summary-init -- you shouldn't need to edit it manually for basic use.

work-summary-kit/
  skills/              # Claude Code skills (entry points)
    daily-summary/     # /daily-summary command
    weekly-summary/    # /weekly-summary command
    summary-init/      # /summary-init setup wizard
  adapters/            # Data source instructions (one per source)
  templates/           # Output format specs
  config/              # Schema + examples
  scheduling/          # Automation templates

1. Create adapters/{source-name}.md with: prerequisites, config fields, collection steps, output fragment, empty state, error handling
2. Add the source to config/config.schema.json
3. Add conditional loading in skills/daily-summary/SKILL.md Step 5
4. Add output section to templates
5. Update skills/summary-init/SKILL.md to ask about the new source

1. Create templates/{name}.md with output format specification
2. Document which sections are included/excluded and the target line count
3. Add the template name to the README

MIT