
git-summarize-weekly
Summarize weekly GitHub contributions for writing weekly reports
- Installs
- 3.4K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zc277584121/mygitplugin --skill git-summarize-weekly- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads git-summarize-weekly automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Git Summarize Weekly
总结本周的 GitHub 贡献,输出适合写入周报的英文摘要。
触发条件
当用户要求总结本周 GitHub 贡献、写周报或查看本周工作时使用此 skill。
执行步骤
-
计算日期范围:计算本周一的日期到今天。使用
date命令计算。 -
拉取 GitHub events:
gh api users/zc277584121/events --paginate --jq '.[]'获取用户近期的 GitHub 活动事件。
-
过滤和分析:
- 过滤出本周时间范围内的事件。
- 默认排除
zc277584121自己账号下的仓库,只保留对他人仓库的贡献。 - 如果用户明确要求包含自己的仓库,则不排除。
- 关注以下事件类型:
PushEvent:代码推送PullRequestEvent:PR 创建/合并PullRequestReviewEvent:PR ReviewIssuesEvent:Issue 创建/关闭IssueCommentEvent:Issue 评论CreateEvent:分支/标签创建
-
输出格式:
- 必须用英文输出,适合直接抄写到周报中。
- 大的 feature 或重要 PR 单独一条列出,简要说明做了什么。
- 小的修复、review、评论等可以合并为一条。
- 按仓库分组,格式简洁清晰。
- 示例格式:
## 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
注意事项
- GitHub Events API 最多返回最近 90 天、300 个事件的数据。
- 如果某一周活动特别少,如实报告即可。
- 输出要简洁实用,直接可以粘贴到周报中。
FAQ
What does the git-summarize-weekly skill do?
Summarize weekly GitHub contributions for writing weekly reports
How do I install git-summarize-weekly?
Run npx skills add https://github.com/zc277584121/mygitplugin --skill git-summarize-weekly in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/git-summarize-weekly/ (personal) or .claude/skills/git-summarize-weekly/ (project).
Which AI agents can use git-summarize-weekly?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is git-summarize-weekly safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains git-summarize-weekly?
It is published by zc277584121 in zc277584121/mygitplugin. It has 3,363 recorded installs.
More from zc277584121/mygitplugin
git-create-repo
zc277584121/mygitplugin
Create a new GitHub repository and clone it locally
git-commit-push
zc277584121/mygitplugin
Commit changes and push to origin without creating a PR
git-commit-pr
zc277584121/mygitplugin
Commit changes and create a pull request to the official upstream repo
git-fork-clone
zc277584121/mygitplugin
Fork a GitHub repo and clone it locally with proper remote setup
git-get-notification
zc277584121/mygitplugin
Check GitHub notifications and recent Issues/PRs for monitored repos
git-sync-main
zc277584121/mygitplugin
Sync local main branch with the latest code from official upstream or origin remote
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.