work-report

What This Skill Does

The work-report skill is an intelligent productivity tool designed to automate the often tedious process of drafting daily and weekly work reports. By leveraging your local Git commit history, the skill scans your workspace to identify completed tasks across multiple repositories. It intelligently parses commit subjects, filters out low-value technical noise (like "merge conflicts"), and translates them into professional, business-friendly Chinese task summaries. The skill automatically structures these summaries into a clear, date-stamped format, ensuring you spend less time writing reports and more time executing tasks.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/leeguooooo/work-report

Use Cases

• Daily Standups: Quickly generate a summary of your day’s progress before a team meeting.
• Weekly Performance Review: Aggregate a week's worth of contributions to create a comprehensive report for your manager.
• Multi-Repo Tracking: Easily consolidate work done across different projects or microservices into a single, cohesive view.
• Professional Reporting: Automate the transformation of rough Git logs into polished, actionable list items that highlight project achievements.

Example Prompts

1. "帮我发一下日报，总结一下今天在各项目里的工作进展。"
2. "今天工作有点忙，请根据我的 git 提交记录写一份周报。"
3. "我想查看过去一周的工作情况，请生成一份包含所有仓库代码变动的周报。"

Tips & Limitations

• Configuration: Ensure your Git user identity is correctly set, as the skill uses git config --global user.name to identify your contributions. If you work across multiple accounts, use the --author flag.
• Workflow Logic: The skill prioritizes directories containing a .git folder. If you have nested repositories, they will be included automatically. If no commits are found within the specified period, the skill will gracefully prompt you for manual input to complete your report.
• Customization: While the skill defaults to normalization for professional language, you can use --no-normalize if you require raw commit logs for technical audit purposes.
• Environment Variables: For seamless operation, set WORK_REPORT_ROOT or CODEX_WORK_ROOT to your primary development directory, eliminating the need to specify the path every time you invoke the skill.