Generate evidence-based project weekly reports from a local code repository. Use when the user asks for a project weekly report, weekly update, status summar...
Documents
Weekly Report
Try itGenerate structured weekly work reports from Git commit history and file-change statistics. Use when the user asks for a weekly report, work summary, progress review, or sprint recap based on repository activity, or when they need a Markdown report of what changed in a project over a time range.
What it does
Generate structured weekly work reports from Git commit history and file-change statistics. Use when the user asks for a weekly report, work summary, progress review, or sprint recap based on repository activity, or when they need a Markdown report of what changed in a project over a time range.
The skill document
Weekly Report Generator
Generates a structured Markdown weekly report from a Git repository's commit history and file-change statistics.
When to use
Use this skill when the user asks to:
- Create a weekly / daily / sprint work report from Git history
- Summarize what changed in a project over a date range
- Produce a Markdown progress report for a team standup
Workflow
- Confirm scope: Ask for the repository path (default: current directory), the number of days to cover (default: 7), and optionally an author filter.
- Collect commits: Run
git logover the time range with a stable format. - Collect file changes: Count files touched in the same range.
- Generate the report: Fill in the template below and write it to
weekly-report.md(or the requested output path). - Review with the user: Summarize highlights and let the user adjust narrative sections.
Collecting data
Collect commits with a compact, parseable format:
git log --since="2026-08-25 00:00:00" --pretty=format:"%h|%ad|%an|%s" --date=short
Count changed files (excluding merge commits for cleaner stats):
git log --since="2026-08-25 00:00:00" --no-merges --name-only --pretty=format:"" | sort -u | wc -l
If the path is not a Git repository, fall back to listing files modified within
the time range (by LastWriteTime) and build the report from that, noting the
method in the report.
Report template
# 周报 Weekly Report
**报告周期**: 2026-08-25 ~ 2026-08-31
**提交总数**: N | **涉及文件**: M | **参与者**: 2
## 本周完成
- (按提交摘要归纳,用项目符号列出要点)
## 进行中
- (未完成/进行中的工作)
## 问题与风险
- (阻塞项或风险,无则写"无")
## 下周计划
- (占位,由用户补充)
## 提交明细
| 提交 | 日期 | 作者 | 说明 |
|------|------|------|------|
| a1b2c3d | 08-26 | Alice | ... |
Automated script (Windows)
On Windows PowerShell, an automated version is bundled:
powershell -ExecutionPolicy Bypass -File scripts/generate-report.ps1 -Repo . -Days 7 -Output weekly-report.md
Parameters:
| Parameter | Default | Description |
|---|---|---|
-Repo | . | Path to the Git repository |
-Days | 7 | Number of days to cover |
-Author | (all) | Only include commits by this author |
-Output | weekly-report.md | Output Markdown file |
The script runs git log, aggregates stats, and writes the filled template.
Notes
- Keep the commit list to at most 50 rows; group or trim older items.
- Narrative sections ("本周完成" etc.) are drafted by the agent from commit summaries, then confirmed with the user.
- Non-Git fallback: if the folder is not a repo, list files modified in the range and mark the report as "based on file timestamps".
Additional resources
- For sample reports and before/after examples, see examples.md
Related skills
This skill is triggered when the user needs to generate, summarize, or organize a weekly work report. It automatically reads all MARKDOWN(.md) daily report files in the local folder C:\Users\zsj\Desktop\WorkBuddyFile, identifies daily reports of the current week, integrates scattered work content, r
Generate polished Chinese R&D weekly reports from recent work logs, chat history, commit notes, or development notes. Use when the user asks to 生成、整理、润色、汇总本周...
Generate structured summaries of recent git commit activity. Use when the user asks for a commit summary, changelog draft, standup notes from git, or to understand what changed in a repo over a time range. Supports filtering by author, date range, and output format.
Generate a compact weekly changelog from a git repository, grouped by author and day, without any dependencies. Use when you need a one-page summary of the last 7 days (or custom window) of commits for a report, standup, or release notes.
Generate a 1-on-1 brief from GitHub activity. Fully deterministic pipeline — 5 tool calls, zero sub-agent spawns.