work-report

Generate daily or weekly work reports from git commits across repositories.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/SennTse/openclaw-backup --skill work-report-senntse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-report
Source: https://github.com/SennTse/openclaw-backup/tree/main/skills/work-report
Command: npx skills add https://github.com/SennTse/openclaw-backup --skill work-report-senntse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill turns Git commit activity into readable daily or weekly work reports across multiple repositories, saving time on status updates and coordination.

Core Features & Use Cases

  • Cross-repo aggregation and per-repo grouping across a workspace root.
  • Time range handling with daily/weekly reports and business-language normalization for readable output.
  • Flexible output formats with per-project lists and optional diff/subject summaries.

Quick Start

Provide the workspace root and whether you want a daily or weekly report, then run the script to generate the formatted report.

Frequently Asked Questions about work-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily work report from git commits across multiple repositories?

To generate a daily work report from git commits, provide a local workspace root directory and specify the daily period to aggregate commit activity across multiple repositories. The script automatically groups results by repository for easy consumption.

Can I aggregate git commit logs from multiple repos into a single weekly summary?

Yes, you can aggregate git commit logs into a weekly summary by specifying the weekly period. The script scans the workspace root and groups the aggregated commit history per repository for easy consumption.

Do I need a local git workspace to extract commit messages for status updates?

Yes, you need a local git-enabled workspace to extract commit messages for status updates. The script operates directly on local repository history rather than remote APIs to generate readable work reports.

What is the best way to normalize git commit subjects into readable business language?

The best way to normalize git commit subjects into readable business language is using the optional normalization feature during report generation. This transforms technical commit messages into concise summaries suitable for coordination updates.

What summary sources can I use when generating git commit reports?

You can use commit subjects, diffs, or both as summary sources when generating git commit reports. This flexibility allows you to choose the level of technical detail included in the final daily or weekly output.