daily-digest
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseNote: If you haveinstalled locally, you should usemcporterto invoke the MCP tool instead of directly calling the MCP tool. ThemcporterCLI provides a more convenient interface and better error handling.mcporter
注意:如果您本地安装了,应使用mcporter调用MCP工具,而非直接调用MCP工具。mcporterCLI提供了更便捷的界面和更完善的错误处理。mcporter
Daily Digest via Gitee MCP
通过Gitee MCP生成每日摘要
Aggregate unread notifications, pending PRs, and open Issues from Gitee to generate a daily work summary.
聚合Gitee上的未读通知、待处理PR和未关闭Issue,生成每日工作总结。
Prerequisites
前提条件
- Gitee MCP Server configured (tools: ,
list_user_notifications,list_repo_pulls,list_repo_issues)get_user_info - Optional: user can provide a list of repositories to focus on (otherwise inferred from notifications)
- 已配置Gitee MCP Server(工具:、
list_user_notifications、list_repo_pulls、list_repo_issues)get_user_info - 可选:用户可提供需重点关注的仓库列表(否则从通知中推断)
Steps
步骤
Step 1: Get Current User Info
步骤1:获取当前用户信息
Use to retrieve the currently authenticated user's information, used for filtering (e.g., only show tasks assigned to me).
get_user_info使用检索当前已认证用户的信息,用于筛选(例如,仅显示分配给我的任务)。
get_user_infoStep 2: Fetch Unread Notifications
步骤2:获取未读通知
Use to get recent notifications:
list_user_notifications- Filter for unread notifications
- Categorize by type: PR-related, Issue-related, @mentions, comment replies
使用获取近期通知:
list_user_notifications- 筛选未读通知
- 按类型分类:PR相关、Issue相关、@提及、评论回复
Step 3: Fetch Pending PRs
步骤3:获取待处理PR
For repositories the user cares about (extracted from notifications or specified by the user), use :
list_repo_pulls- Filter for PRs
state=open - Focus on:
- PRs assigned to me for review
- My own PRs waiting for review
- PRs with new comments that need a reply
针对用户关注的仓库(从通知中提取或由用户指定),使用:
list_repo_pulls- 筛选的PR
state=open - 重点关注:
- 分配给我审核的PR
- 我发起的等待审核的PR
- 有新评论需要回复的PR
Step 4: Fetch Open Issues
步骤4:获取未关闭Issue
Use :
list_repo_issues- Filter for Issues assigned to me
state=open - Filter for open Issues I created
使用:
list_repo_issues- 筛选分配给我的的Issue
state=open - 筛选我创建的未关闭Issue
Step 5: Generate Daily Digest
步骤5:生成每日摘要
undefinedundefinedDaily Work Digest
Daily Work Digest
📅 [date] 👤 [username]
📅 [date] 👤 [username]
📬 Unread Notifications ([N])
📬 Unread Notifications ([N])
@Mentions
@Mentions
- [repo] [Issue/PR title] - [notification summary]
- [repo] [Issue/PR title] - [notification summary]
PR Comments
PR Comments
- [repo] PR #N [title] - [comment summary]
- [repo] PR #N [title] - [comment summary]
Issue Updates
Issue Updates
- [repo] Issue #N [title] - [update summary]
- [repo] Issue #N [title] - [update summary]
🔀 Pending PRs
🔀 Pending PRs
Needs My Review
Needs My Review
| Repo | PR | Author | Updated |
|---|---|---|---|
| [repo] | #N [title] | [@author] | [time] |
| Repo | PR | Author | Updated |
|---|---|---|---|
| [repo] | #N [title] | [@author] | [time] |
My PRs Awaiting Review
My PRs Awaiting Review
| Repo | PR | Status | Updated |
|---|---|---|---|
| [repo] | #N [title] | [Awaiting review / Has new comments] | [time] |
| Repo | PR | Status | Updated |
|---|---|---|---|
| [repo] | #N [title] | [Awaiting review / Has new comments] | [time] |
📋 My Open Issues
📋 My Open Issues
| Repo | Issue | Priority | Status |
|---|---|---|---|
| [repo] | #N [title] | P1 | In progress |
| Repo | Issue | Priority | Status |
|---|---|---|---|
| [repo] | #N [title] | P1 | In progress |
Today's Suggestions
Today's Suggestions
Handle first:
- [Most urgent item, e.g., a review request blocking someone else]
- [Second priority item]
Can defer:
- [Low priority items]
If there is nothing pending:
Handle first:
- [Most urgent item, e.g., a review request blocking someone else]
- [Second priority item]
Can defer:
- [Low priority items]
若没有待处理事项:
Daily Work Digest
Daily Work Digest
📅 [date]
All clear! No pending PRs, Issues, or unread notifications.
undefined📅 [date]
All clear! No pending PRs, Issues, or unread notifications.
undefinedNotes
注意事项
- The digest focuses on information aggregation, not deep analysis
- If there are many repositories, prioritize time-sensitive items
- Notifications may span multiple repositories — group them clearly
- 摘要侧重于信息聚合,而非深度分析
- 若涉及多个仓库,优先处理时间敏感的事项
- 通知可能涉及多个仓库——需清晰分组