Weekly Report Generation

When to Use

• When users say "Help me write a weekly report" or "What did I do this week";
• Before leaving work on Friday or before a report, need to organize this week's work;
• When git history is available and you want to quickly turn commits into weekly report materials.

Usage Steps

Step 1: Confirm Time Period and Scope

• Default is from this Monday to now; you can also specify start and end dates according to report requirements;
• When multiple repositories are involved, list all paths at once;
• Confirm who the weekly report is for (yourself, team leader, client), as the tone and granularity will differ.

Step 2: Collect Facts

Step 3: Supplement Work Beyond Commits

• Meetings, reviews, communication, coordination;
• In-progress items and their progress;
• Risks, blockers, needs for others' cooperation;
• Next week's plan.

Step 4: Compose the Weekly Report

# Weekly Report: 2026-08-24 ~ 2026-08-30

## Completed This Week
- Group by type or project, each item is a sentence of "what was done", which can include commit IDs
## In Progress
- Item + current progress
## Risks & Blockers
- State problems directly and specify the support needed
## Next Steps
- Executable and prioritized

• Conclusions are more important than quantity: Write "Launched feature X" instead of "Made 20 commits";
• Put commit IDs in parentheses as evidence, do not occupy the main text;
• Trivial commits are not included in the main text.

Step 5: Deliver After Confirmation

• Let the user review to ensure no exaggeration or omission of key work;
• If archiving or sending to a group, output files or provide text directly as required by the user.

Input and Output

• Input: git repository paths (multiple optional) + time range + work items supplemented by users;
• Output: Structured Chinese weekly report.

Examples

- Total commits: 45 (excluding merge), files involved: 182
### feat (6)
- [1ef9857] feat: API testing skill adds contract-to-test skeleton generation script (Laffey-82)

## Completed This Week
- API testing skill adds contract-to-test skeleton generation script, which directly rejects failed contract validation (1ef9857)
- Task breakdown and technical documentation skills add check scripts, enabling machine self-inspection of outputs (45efbeb, 651ea4b)
## In Progress
- New skill weekly report generation, skeleton completed, currently supplementing actual tests
## Risks & Blockers
- None
## Next Steps
- Release v0.8.0 after completing actual tests for the new skill

Auxiliary Script

# This Monday to now, current directory repository
python skills/weekly-report/scripts/collect_worklog.py

# Specify time period + multiple repositories, output to file
python skills/weekly-report/scripts/collect_worklog.py --since 2026-08-24 --until 2026-08-30 --repos <path1> <path2> -o draft.md

Notes

• No fabrication: Do not write content not collected by the script or confirmed by the user;
• Distinguish facts and conclusions: Commits are facts, "what was done" is a conclusion, which needs to be confirmed by humans;
• Write fewer technical details in weekly reports for leaders, while more implementation details can be included for team members;
• When summarizing multiple repositories, group by repository or project, do not mix them together.

Unsuitable Scenarios

• No git history or work records, need to write a weekly report out of thin air;
• Users need a daily report (just adjust the time range to one day);
• Pure personal log without the need for structure.

Verification Methods

1. Trigger: "Help me write a weekly report";
2. Run the script: The output of collect_worklog.py is consistent with the spot check results of git log;
3. Review: Each "Completed" item in the weekly report can correspond to a commit or a user-confirmed item;
4. Confirmation: No objections from the user after review.