write-weekly-report

Generates Chinese weekly report Excel files from Git commits with weighted hour allocation.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill write-weekly-report-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-weekly-report
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/write-weekly-report
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill write-weekly-report-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @oai/artifact-tool, and includes scripts (resource) components.

What problem does it solve? Turning a week of scattered Git commits into a structured weekly report with defensible hour allocation is tedious and error-prone. This Skill reads commit history across one or more repositories, semantically groups commits into tasks, and produces a formatted Chinese Excel report where task hours sum exactly to your stated total. ## Core Features & Use Cases - Git Evidence Collection: Filters commits by author (default Ouyangfan, case-insensitive) and date range using half-open intervals, capturing subject, body, and change statistics. - Semantic Task Grouping: Merges commits into 5-8 project/module tasks based on shared paths and scope, without fabricating business outcomes. - Weighted Hour Allocation: Distributes a user-provided total hour budget across tasks using largest-remainder rounding at a configurable precision (default 0.5h), guaranteeing the sum matches exactly. - Formatted Excel Output: Builds a styled .xlsx via @oai/artifact-tool with merged project/module cells, frozen header, and a rendered PNG preview for visual verification. - Use Case: On Friday afternoon, ask for a report of last week's commits with a 40-hour total; receive 周报_YYYY-MM-DD_YYYY-MM-DD_Ouyangfan.xlsx ready to submit. ## Quick Start Ask the agent to summarize your commits from last week across your repositories into a weekly report Excel, telling it your total hours such as 40.

Frequently Asked Questions about write-weekly-report

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

FAQPage Schema
How do I generate a weekly report from Git commits?▼

Provide the target repositories, date range, and your total hours. The skill filters commits by author, groups them into 5-8 semantic tasks by project and module, allocates hours by weighted workload, and exports a formatted Excel file.

How are task hours allocated in the weekly report?▼

Hours are allocated by relative workload weights using largest-remainder rounding at a configurable precision (default 0.5 hours). Commit counts and line changes inform weights but are never used directly as hours, and the allocated sum always equals your stated total exactly.

Can I filter Git commits by a specific author?▼

Yes, the default author is Ouyangfan with case-insensitive matching on name and email, and you can override it explicitly. Commits from other authors are excluded, and the skill never guesses authorship from ambiguous data.

What happens if no commits are found in the date range?▼

The skill reports that no matching commits were found and does not fabricate tasks or hours. An empty template is only generated if you explicitly request one.

What format is the weekly report output file?▼

The output is an .xlsx file named 周报_start_end_author.xlsx built with @oai/artifact-tool. It contains a fixed five-column header, vertically merged project and module cells, frozen header row, and a numeric hours column.