work-report-generator

Generate daily and weekly progress reports from git history.

2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Throokie/claude-code-skills --skill work-report-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-report-generator
Source: https://github.com/Throokie/claude-code-skills/tree/main/skills/work-report-generator
Command: npx skills add https://github.com/Throokie/claude-code-skills --skill work-report-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

daily 和 weekly 的代码提交记录需要整理成可分享的进度报告。本 Skill 将自动从 Git 提交历史中提炼要点,生成清晰、可追溯的日报与周报。

Core Features & Use Cases

  • 自动从仓库的提交记录生成日/周报摘要,包含提交数量、活跃日、变更文件等关键信息。
  • 支持跨仓库聚合与按日期分组,方便 sprint 回顾与对外汇报。
  • 生成的 Markdown/文本报告可直接用于文档、看板或 PR/合并请求中的简报。

Quick Start

直接运行工作流,指定目标时间段,系统将输出今日与本周的报告。

Frequently Asked Questions about work-report-generator

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

FAQPage Schema
How do I generate a weekly progress report from git commit history?

Generate a weekly progress report from git commit history by parsing repository logs, aggregating commits by date, and formatting the summarized code activity into a markdown-ready summary for sprint reviews.

Can I aggregate git commits across multiple repositories for a daily report?

Yes, you can aggregate git commits across multiple repositories for a daily report. The system parses git logs from various branches and groups them by date to summarize cross-repository code activity.

What is the best way to automate daily and weekly code activity summaries for stakeholders?

Automating daily and weekly code activity summaries involves parsing git history to extract commit counts and changed files, then formatting these time-bound, auditable outputs into markdown for stakeholder updates.

Does the generated git activity report support markdown formatting for pull requests?

Yes, the generated git activity report supports markdown formatting. The summarized daily and weekly outputs are markdown-ready, allowing direct integration into documentation, task boards, or pull request briefs.

What information is included in a git commit summary for sprint reviews?

A git commit summary for sprint reviews includes the number of commits, active days, and changed files. It parses git history to provide auditable, time-bound code activity reports grouped by date.

Do I need any extra dependencies to format git logs into markdown summaries?

No extra dependencies are required to format git logs into markdown summaries. The system independently parses git history and formats the aggregated code activity into text-ready reports without external components.