monthly-report
monthly-report
Turns a month of raw release notes into a monthly work report (月报). The input is version-ordered; the output is capability-domain-ordered. That regrouping is the entire value of this skill — a report that walks v2.2, v2.3, v2.4 in sequence is just the changelog again, and the reader learns nothing about what the month built.
Output language is Chinese, because that is what the report is written in. Section headings below are literal output text, not instructions.
Step 0 — Locate input and output
Default convention:
| Path | |
|---|---|
| Input | tmp/work/i/{month}.md — e.g. 5.md for May |
| Output | tmp/work/o/{month}.md |
If the user pastes the content directly, use that. If a prior month's output exists (tmp/work/o/{month-1}.md), read it first — it is the format contract. Match its heading scheme, section ordering, and level of detail rather than the template below.
Work the user mentions in chat but that is absent from the changelog (a side deliverable, another repo, a mini-program, cross-team work) still belongs in the report. It usually becomes its own late section — see o/5.md's 微信媒资小程序 section, which had no counterpart in the input.