技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 117 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：andrew020/daily-commits
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill's instructions match its stated purpose (summarizing a user's git commits for a date) and do not request unrelated credentials or installs, though it implicitly requires a local git repository and the git binary which are not declared.
目的
The skill's name and description match the instructions (it runs git log, groups commits by feature areas, and formats a summary). However, the registry metadata lists no required binaries while the SKILL.md explicitly runs git commands — the skill implicitly requires access to a local git repository and the git binary being available on PATH. That omission is a minor coherence gap to surface to users.
说明范围
SKILL.md confines actions to running git log (with and without --stat) filtered by date and author, analyzing commit messages and file paths, and producing a grouped summary. It does not instruct reading unrelated system files, contacting external endpoints, or accessing credentials. One small ambiguity: it asks the agent to convert the YYYY.MM.DD input into git --after/--before timestamps but does not define timezone handling; the user/agent …
安装机制
There is no install spec (instruction-only), so nothing will be downloaded or written to disk by an installer. This is low-risk. The only runtime requirement is that git is present in the environment and the agent can execute shell commands (Bash).
证书
The skill declares no environment variables or credentials, and the instructions do not access secrets. The main capability is read access to the repository and commit history, which is proportionate to the stated purpose.
持久
The skill is not always-enabled and does not request elevated persistent privileges. Autonomous invocation is allowed (platform default), but there is no sign it attempts to modify agent/system configuration or other skills.
综合结论
This skill will run git commands in whatever working directory the agent is given, so it needs (1) the git binary available on PATH and (2) to be run inside the repository whose commits you want summarized. It will read commit messages, stats, and file paths — essentially reading repo history and metadata — so only use it where you are comfortable allowing the agent to view that code/logs. Also confirm how you want date boundaries handled (tim…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Summarize a person's git commits for a specific date, grouped by feature points, in English. Use when reviewing daily work output.」。简介：Summarize a person's git commits on a given date, grouped by feature area with …。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/andrew020/daily-commits/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: daily-commits
description: Summarize a person's git commits for a specific date, grouped by feature points, in English. Use when reviewing daily work output.
argument-hint: [date:YYYY.MM.DD] [author-name]
allowed-tools: Bash, Read
---
# Daily Commits Summary
Summarize all git commits by **$1** on **$0**, grouped by feature/functional area, in English.
## Steps
1. Run `git log` filtered by date and author:
```
git log --after="<start-of-day>" --before="<end-of-day>" --author="$1" --pretty=format:"%h %s" --no-merges
```
Convert the date `$0` (format: `YYYY.MM.DD`) to proper git date range:
- `--after` = the date at 00:00:00
- `--before` = the next day at 00:00:00
2. Also run `git log` with `--stat` to understand the scope of changes:
```
git log --after="<start-of-day>" --before="<end-of-day>" --author="$1" --stat --no-merges
```
3. Analyze all commits and group them by feature/functional area based on:
- Commit message prefixes (feat, fix, refactor, docs, style, test, chore, etc.)
- Related file paths and modules
- Logical grouping of related changes
4. Output a clean summary in this format:
```
## Daily Commits Summary: <author> — <date>
### <Feature Area 1>
- <concise description of what was done> (`commit-hash`)
- ...
### <Feature Area 2>
- <concise description of what was done> (`commit-hash`)
- ...
**Total: X commits**
```
## Rules
- Output in **English** only
- Group by logical feature, not by commit type prefix
- Each bullet should be a concise human-readable description (not just the raw commit message)
- If a commit message already has a conventional prefix like `feat(meeting):`, use the scope as a hint for grouping
- Omit merge commits
- If no commits found, state that clearly