About this skill

Problem

Engineering weekly reports often stall on manual collection: copying commit messages, estimating code changes, and backfilling TAPD task status. This skill pulls together Git commits, TAPD stories, bugs, and iteration data into one structured report workflow.

How It Works

Inferred parameters: author from git config, repositories from remote URLs, and period from phrases such as “weekly report,” “monthly report,” or “last week.”
Git statistics: collects commit lists, changed files, and additions/deletions, separating business code from assets, vendor files, docs, and other non-code changes.
TAPD tracking: when TAPD MCP is configured, it retrieves iterations, requirements, and bugs, aggregates them by status, owner, and fixer role, and preserves detail links.
Period breakdown: splits the range into weekly sections based on natural weeks or week_cycle, producing deliverable tables, contribution highlights, and a shareable plain-text summary.

Boundaries

It works best when repository access and commit history are available. If local repositories are missing, remote URLs are unparseable, or TAPD MCP is not configured, the user must provide missing parameters or accept a Git-only report.

Screenshots

Use Cases

Compile last week's personal commits, code changes, and deliverables into a team report.
Summarize monthly Git activity and TAPD story/bug status into one statistics table.
Separate business code changes from vendor or asset changes for a phase review.
Generate commit stats from a provided Gongfeng repo path and date range.