agentleFS
leonsong09leonsong09/commit-daily-summary/SKILL.md

commit-daily-summary

Skill9 starsChanged 8 months agoMITView on GitHub

Use when the user wants a same-day summary of git commits or a commit-based daily report, asks what they did today, or says 总结我今天做了什么, 总结我的提交, 提交总结, 今天提交总结, 日报.

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 · 1

    1. borgesme/fastapi-general-template★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn one day of git commits into a readable work summary.

    line 10
  2. Distinctive:

    Default scope is today in the user's local timezone unless the user gives a date.

    line 14
  3. Distinctive:

    Prefer git evidence over memory.

    line 15
  4. Distinctive:

    Do not include empty, noise-only, or clearly meaningless commits as standalone achievements.

    line 18
  5. Distinctive:

    Use direct git commands with explicit repository paths.

    line 35
  6. Distinctive:

    If no commits are found, state that clearly.

    line 43
  7. Distinctive:

    Do not create one task sentence per commit if several commits are obviously part of the same workstream.

    line 53
  8. Distinctive:

    start with a clear action verb

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

commit-daily-summary

Overview

Use this skill to turn one day of git commits into a readable work summary. The goal is not to dump commit lines, but to translate them into grouped, human-friendly task statements.

Core Rules

  • Default scope is today in the user's local timezone unless the user gives a date.
  • Prefer git evidence over memory.
  • Group commits by workstream / theme, not just by repository order.
  • Rewrite raw commit messages into concise Chinese action summaries.
  • Do not include empty, noise-only, or clearly meaningless commits as standalone achievements.

Workflow

Step 1: Determine the date and repo scope

Default assumptions:

  • date range: today
  • repository scope: current repository unless the user asks for multiple repositories

Clarify only when necessary:

  • today vs a specific date
  • current repo vs multiple repos
  • whether the user wants only task summaries or task summaries + raw commit details

Step 2: Collect commits

Use direct git commands with explicit repository paths.

Recommended command pattern:

git -C <repo> log --since="YYYY-MM-DD 00:00" --until="YYYY-MM-DD 23:59:59" --pretty=format:"%h%x09%s"

If no commits are found, state that clearly.

Step 3: Group commits into workstreams

Cluster related commits together, for example:

  • 同一功能开发
  • 同一缺陷修复
  • 同一配置或工具链调整
  • 同一文档更新

Do not create one task sentence per commit if several commits are obviously part of the same workstream.

Step 4: Rewrite into Chinese action summaries

Good summary lines should:

  • start with a clear action verb
  • describe the actual business or engineering result
  • omit noisy implementation trivia unless it matters
  • be understandable to someone reading a daily report quickly

Examples:

  • 实现了行情页的筛选条件持久化
  • 修复了任务轮询在终态下未刷新概览的问题
  • 重构了图表数据映射逻辑,降低了重复处理分支
  • 补充了设置保存链路的回归测试

Step 5: Output the daily report

Preferred structure:

  • 日期范围
  • 今日工作摘要
  • 仓库 / workstream 明细
  • 如有需要,再附原始 commits

Recommended Output Shape

## 提交总结

- 日期:2026-03-30
- 范围:today / current repo

### 今日工作摘要
- ...
- ...

### 分项明细
#### 仓库 A
- workstream 1: ...
- workstream 2: ...

### 原始提交(可选)
- abc123 feat(...)

When to Use

  • 用户说“总结我今天做了什么”
  • 用户说“总结我的提交”
  • 用户说“提交总结”
  • 用户要一份基于 commit 的日报

When Not to Use

  • 用户要的是当前会话收尾,而不是 commit 视角
  • 用户要的是跨会话的项目级日报
  • 用户没有 git 提交,真正需要的是工作区变更总结

In those cases, prefer session-wrap or project-daily style skills instead.

Quality Checklist

Before responding, verify:

  • Date scope is explicit
  • Summary is based on actual commits
  • Related commits are grouped into workstreams
  • Chinese task lines are human-readable and action-oriented
  • Empty noise commits are not treated as major work items

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.