About this skill

Problem

Engineers often write weekly reports by manually scanning commit logs across repositories, grouping work by project and type, trimming wording, and sending the result to WeChat. A “last 7 days” window can pull in weekend work or teammates’ commits, while date handling varies across platforms; with multiple repos, manual aggregation can miss or duplicate entries.

How It Works

Reads or records project path, report template, and Git author info, persisting static setup only.
Detects Mac, Linux, and Windows, then filters current-user commits with git -C and --author.
Groups commit messages such as feat, fix, refactor, and docs into sections like feature development, bug fixes, optimization, and documentation.
Produces a chat version and a plain-text WeChat version; user confirmation is required before sending, and messages over 2000 characters are split by project.
Uses Monday through today as the default range, not a rolling 7-day window.

Boundaries

It does not inspect file diffs and relies on commit messages; it does not store runtime data or report content. Repositories with no commits or per-repo failures are noted at the end. It is suitable for drafting personal weekly reports, not as a complete performance record, and not a substitute for code review or incident analysis. Template rules affect presentation only and do not rewrite commit text.

Screenshots

Use Cases

Before Friday wrap-up, summarize this week’s commits from multiple service repos into a manager-ready report, then preview and send it via WeChat.
Switch between Mac and Windows machines, then collect personal commits from Monday to today using the same weekly report template.
When commits are spread across repositories, group feat, fix, and docs messages into feature, bug, and documentation sections.
When the weekly report exceeds the WeChat single-message limit, split it into plain-text project messages with batch labels.

Best For

Backend engineers: turn personal commits from multiple service repos into a structured weekly report for their manager.
Frontend developers: group feat, fix, and style commits by project to avoid manually copying commit logs.
Junior team members: generate a weekly summary that follows their historical report style, with human confirmation before sending.
Independent developers: working across Mac, Linux, and Windows, needing a stable Monday-to-today commit range.