Summarize this week's GitHub contributions and output an English summary suitable for a weekly report.
Trigger conditions
Use this skill when the user asks to summarize this week's GitHub contributions, write a weekly report, or review this week's work.
Execution steps
-
Calculate the date range: Calculate from this Monday's date to today. Use the
datecommand to calculate. -
Fetch GitHub events:
gh api users/zc277584121/events --paginate --jq '.[]'Get the user's recent GitHub activity events.
-
Filter and analyze:
- Filter out events within this week's time range.
- By default, exclude
zc277584121repositories under your own account, keeping only contributions to others' repositories. - If the user explicitly requests including their own repositories, do not exclude them.
- Focus on the following event types:
PushEvent: code pushesPullRequestEvent: PR creation/mergesPullRequestReviewEvent:PR ReviewIssuesEvent: Issue creation/closuresIssueCommentEvent: Issue commentsCreateEvent: branch/tag creation
-
Output format:
- Must output in English, suitable for directly copying into a weekly report.
- List large features or important PRs as separate entries, briefly explaining what was done.
- Small fixes, reviews, comments, etc. can be merged into one entry.
- Group by repository, with a concise and clear format.
- Example format:
## Weekly Contributions (2025-01-20 ~ 2025-01-24) ### milvus-io/pymilvus - Implemented hybrid search API with support for multiple vector fields (#xxx) - Fixed connection pool timeout issue (#xxx) - Reviewed 3 PRs related to batch insert optimization ### milvus-io/milvus - Minor: commented on 2 issues about memory management
Notes
- The GitHub Events API returns at most 300 events from the last 90 days.
- If there is particularly little activity in a given week, just report it truthfully.
- The output should be concise and practical, ready to paste directly into a weekly report.