agentleFS
sdh0219sdh0219/team-memory/skills/team-digest/SKILL.md

team-digest

Skill2 starsChanged 22 days agoMITView on GitHub

把项目的 .memory/LOG.md 与 git log 蒸馏成周报/日报等进度摘要,回答"这段时间 agent 们都干了啥", 是 team-memory(面向下一个 agent 接手)的配套技能:team-memory 服务"谁接手",本 skill 服务"项目主人看进度"。 触发场景:用户要周报 / 日报 / 进度摘要 / digest / standup 汇报;用户问"这周 agent 们干了啥 / 这段时间项目进展如何"; 阶段性复盘、向团队或上级同步项目状态时。 边界:只蒸馏 .memory 与 git 里可验证的事实,不编造数据;项目还没有 .memory/ 记忆层时, 先建议初始化 team-memory,不凭空写报告。

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jiahao-shao1/sjh-skills★ 43same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

Files
SKILL.md

Team Digest — 项目进度蒸馏报告

把 .memory/LOG.md 和 git log 蒸馏成一份三分钟读完的周报/日报,回答"这段时间 agent 们都干了啥"。 team-memory 面向"下一个 agent 接手",本 skill 面向"项目的主人看进度"——素材是同一套记忆文件, 读者和视角不同:只留结论,砍掉过程。

确定周期

  • 默认最近 7 天。
  • 用户说"日报"取 1 天,"周报"取 7 天;也可以指定区间(如"上周""10 月 1 日到今天")。
  • 报告标题里写清实际起止日期,别让读者猜周期。

数据源与命令

按顺序取数,三方互相核对:

  1. .memory/LOG.md — 挑出日期落在周期内的条目;"遗留"字段单独收集,它是本期风险清单的直接来源。
  2. git log — 核对 LOG 是否漏记,顺手取数字:

    git log --since="YYYY-MM-DD" --oneline --no-merges   # 周期内的提交
    git shortlog -sn --since="YYYY-MM-DD"                # 各 agent/作者活跃度
  3. .memory/STATE.md — 读"正在做"小节作为"进行中"的内容;"坑与约定"可补充进风险清单。

蒸馏流程

  1. 按主题聚类,不按时间流水账:把 LOG 条目和 commit 归进"支付打通 / 文档补齐 / 修复崩溃"这类主题, 同一主题的多条记录合并成一件事。
  2. 每个主题一句话结论,写"达成了什么",不写"过程中做了哪些动作"。
  3. 三栏分清:完成(本期做完)、进行中(STATE.md 的"正在做")、遗留(LOG 的"遗留"字段),不混写。
  4. 数字必须真实数出来:commit 数、参与者数、改动文件数都来自命令实际输出,禁止编造或估算。 改动文件数可用 git diff --name-only "起点"..HEAD 统计并去重。

输出模板

# 项目周报 · YYYY-MM-DD ~ YYYY-MM-DD

## 一句话总览
<本周期最重要的一件事,一句话>

## 本期完成(按主题,每条注明来源:LOG/commit)
- <主题>:<一句话结论>(来源:LOG 2026-10-24 / commit a1b2c3d)

## 进行中(来自 STATE.md)
- <事项>:<当前进度、卡在哪>

## 遗留与风险(来自 LOG 的"遗留"字段)
- <事项>:<影响与建议的下一步>

## 数字(commits N · 参与者 M · 触及文件 K)
<一行说明数字口径,如:参与者按 git shortlog 计>

周期是 1 天就把标题叫"日报",7 天叫"周报",起止日期替换为实际值。

落点

  • 默认直接在对话里输出报告,不落盘。
  • 用户要求存档时写到 docs/digests/YYYY-MM-DD_YYYY-MM-DD.md(用实际起止日期),并建议 commit 进仓库。

纪律

  • 只引用 LOG 和 git 能验证的事实;没有依据的话不写,确需提示时标注"待确认"。
  • 引用 LOG 原条目时注明日期,方便回溯。
  • 不把密钥、token、内网地址等敏感信息写进报告——即使它们出现在 LOG 里也要照常过滤。
  • LOG 缺失的时间段用 git log 补;两者都没有就明确写"该时段无记录",不猜测。
  • 本 skill 对记忆文件只读;写 STATE/LOG 是 team-memory 的职责,别越界。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.