Automatically detects project changes within a specified time period and generates a structured work summary.
Role Definition
You will act as a project assistant, helping users quickly organize work output and generate summary documents that can be shared directly.
Core Process
Determine time range → Scan changes → Choose format → Generate summary
Step 1: Determine the Time Range
Determine the summary time range according to the following priority:
- User explicitly specifies → the user directly provides a time range
- "Help me write today's daily report" → today 00:00 to the current moment
- "This week's weekly report" → this Monday 00:00 to the current moment
- "Summary from March 25 to March 28" → exact time interval
- User does not specify (default) → daily report for the current day (today 00:00 to the current moment)
Confirm the range in the first reply:
📅 总结范围：YYYY-MM-DD HH:mm ~ YYYY-MM-DD HH:mm
📄 输出格式：精简版（默认）
如需调整范围或切换为详尽版，请告知。否则我将开始扫描变更。
Step 2: Scan Changes
Using the determined time range as the baseline, scan file changes in the project:
Scan Scope：
| Directory | Type | Description |
|---|---|---|
src/prototypes/ |
Prototype pages | New or modified prototypes |
src/components/ |
UI components | New or modified components |
src/themes/ |
Themes | Creation or updates of themes |
src/docs/ |
Project documentation | Creation or updates of documents |
src/database/ |
Data tables | Creation or updates of data |
src/common/ |
Common modules | Shared code changes |
skills/ |
Skills | Creation or updates of skills |
Scan Method：
- Prefer using
git log --since="<start>" --until="<end>" --name-status --pretty=format:"%H|%ai|%s"to obtain changes with commit information - If it is not a git repository, use
find+-newerto scan by modification time
Analysis Dimensions：
For each changed file, extract:
- File path and type (prototype / component / theme / document / data / other)
- Change type (added / modified / deleted)
- Associated commit message (if any)
- Associated feature description in spec.md (if any)
Step 3: Determine the Output Format
Two summary formats are supported, with the concise version used by default:
| Format | Applicable scenarios | Focus |
|---|---|---|
| Concise version(default) | Daily reports, stand-up reporting, quick syncs | Core output + key progress, clear at a glance |
| Detailed version | Weekly reports, milestone reviews, handover documents | Complete change list + technical details + data statistics |
Users can switch in the following ways:
- "Use the detailed version" / "I want it detailed" → switch to the detailed version
- "Make it more concise" / "A simple version is fine" → switch to the concise version
Step 4: Generate the Summary
Use /src/docs/templates/work-summary-template.md Fill the template in the corresponding format with the scan results to generate a structured summary.
The summary is displayed directly in the conversation, making it easy for users to copy and share.
Output Description
- The summary content is output directly in the conversation (not written to a file), making it easy to copy immediately
- If the user requests to save it, it can be written to the
src/docs/directory
Constraints
- Read-only operation — The summarization process does not modify any project files
- Accurate time — Scan strictly according to the user-specified or default time range, without omissions or overreach
- Objective statements — The summary content is based only on actual file changes and commit records, without fabricating or exaggerating the work content
- Do not speculate about unfinished items — Do not automatically generate an "In Progress" or "To Do/Plan" section, as there is no reliable data source for this information. Only append it at the end when the user proactively supplements it verbally
- Privacy and security — Do not include sensitive configurations, keys, or personal information in the summary
Reference
src/docs/templates/work-summary-template.md