Token导航 LogoToken导航

Agent Skill · 前端设计

daily-commit-summary(每日提交摘要)

daily-commit-summary 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

daily-commit-summary 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,045。

总安装 563周安装 23GitHub Stars 公开资料未说明下载 182核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:daily-commit-summary(每日提交摘要)
来源仓库:https://github.com/habonn/portal-skills
仓库路径:skills/daily-commit-summary
安装命令:
npx skills add https://github.com/habonn/portal-skills --skill daily-commit-summary
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/habonn/portal-skills --skill daily-commit-summary

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

daily-commit-summary 分析 git 提交历史并转化为人类可读的任务描述,便于复盘每日工作内容。适合远程团队同步进展、个人时间审计或向利益相关者汇报成果时使用。支持多仓库扫描与工作时间过滤,输出按时间段分组呈现以提高可读性。

必须配置 repositories 列表与 author email,否则无法正确关联提交归属。执行前请确保各 repo 处于 clean 状态,避免合并提交干扰摘要准确性。

来源仓库内路径:skills/daily-commit-summary

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/habonn/portal-skills --skill daily-commit-summ…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

daily-commit-summary 怎么安装?

在终端执行 npx skills add https://github.com/habonn/portal-skills --skill daily-commit-summary。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

daily-commit-summary 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

daily-commit-summary 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

daily-commit-summary 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

daily-commit-summary 用的人多吗?

公开数据是累计安装 563 次,近一周安装 23 次,下载 182 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

daily-commit-summary 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
daily-commit-summary

每日提交摘要 · 本页

563—需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Daily Commit Summary Skill

Generate a daily task summary by analyzing git commits and rewriting them into clear, human-readable task descriptions.

When to Use This Skill

  • "What did I do today?"
  • "Summarize my commits"
  • "Daily commit summary"
  • "/daily-commit-summary"

Configuration

~/.daily-commit-summary.yaml:

repositories:
  - ~/projects/portal-api
  - ~/projects/portal-frontend
work_hours:
  start: "08:00"
  end: "18:00"
author: "your.email@example.com"

🚨 CRITICAL: EXECUTION STEPS (MUST FOLLOW IN ORDER)

STEP 1: Collect commits → Run git log commands for each repository

⚠️ IMPORTANT: Git Command Format

NEVER use cd to change directory before running git commands.

❌ WRONG (wastes tokens, often fails):

cd "/path/to/repo" && git log --author="email" ...

✅ CORRECT (use git -C flag):

git -C /absolute/path/to/repo log --author="email" --since="YYYY-MM-DD 08:00" --until="YYYY-MM-DD 23:59" --pretty=format:"%h %s" 2>/dev/null || echo "REPO_NOT_FOUND"

Always use git -C <path> to specify the repository path directly.

STEP 2: TRANSFORM commits to tasks → This is MANDATORY, not optional!

  • Take each commit message
  • Rewrite it as a human-readable task sentence
  • Use action verbs: Fixed, Implemented, Updated, etc.

STEP 3: Output with Tasks FIRST → Tasks section must appear before commit details


⚠️ MANDATORY OUTPUT REQUIREMENTS

YOU MUST ALWAYS INCLUDE THE "Summary Task Daily" SECTION.

This section analyzes raw commits and rewrites them as clear task sentences. This is the PRIMARY purpose of this skill - not just listing commits.

DO NOT just dump raw commits. TRANSFORM them into task sentences.


Required Output Format

📋 Daily Commit Summary
Date: [Day], [Month] [Date], [Year] (08:00 - now)

---

Summary Task Daily

- [Transformed task sentence 1]
- [Transformed task sentence 2]

---

[Rest of commit details...]

Example

Input (raw commits):

b0b0352 fix(notification-template): update mock Thai name to include month
551c5ef chore: update gitignore and mock data
f344b80 []

Required Output:

📋 Daily Commit Summary
Date: Saturday, March 21, 2026 (08:00 - now)

---

Summary Task Daily

- Fixed notification template to correctly display Thai month names in mock data
- Updated project configuration files (gitignore) and mock data for testing

---

📊 Commits Detail

backoffice-portal-next (3 commits)

🔧 fix
- b0b0352 fix(notification-template): update mock Thai name to include month

🔨 chore
- 551c5ef chore: update gitignore and mock data

❓ other
- f344b80 []

Other Repositories

| Repository | Commits |
|------------|---------|
| portal-uam | 0 |
| portal-cube | 0 |
| portal-backend | 0 |
| portal-backend-cms | 0 |

Total: 3 commits today 🎉

🔄 TRANSFORMATION RULES (STEP 2)

Parse commits using Conventional Commits format: <type>(<scope>): <description>

Reference: #[[file:commit/SKILL.md]]

For EACH commit, you MUST transform it like this:

Raw Commit→Transformed Task
feat(auth): add login with Google→Implemented Google login authentication
fix(cart): resolve quantity update issue→Fixed cart quantity update issue
fix(notification-template): update mock Thai name to include month→Fixed notification template to correctly display Thai month names in mock data
chore: update gitignore and mock data→Updated project configuration files (gitignore) and mock data for testing
refactor(api): simplify error handling→Refactored API error handling for better maintainability
perf(query): optimize database lookup→Optimized database query lookup performance
test(auth): add login unit tests→Added unit tests for login authentication
docs(readme): update installation steps→Updated README installation documentation
build(deps): upgrade react to v19→Upgraded React dependency to version 19
ci(github): add deploy workflow→Configured GitHub Actions deploy workflow

Task Writing Rules

  1. Start with action verb: Fixed, Implemented, Updated, Refactored, Added
  2. Be descriptive: Expand abbreviations, add context
  3. Human-readable: Write for standup reports
  4. Group related: Combine multiple commits about same feature
  5. Skip empty: Don't include WIP/empty commits like [] as tasks

Grouping Example

Multiple related commits:

feat(auth): add login page
feat(auth): add password validation
fix(auth): resolve token issue

→ ONE analyzed task:

- Implemented user authentication system with login page and password validation

Commit Type → Task Language

Reference: Uses Conventional Commits format from #[[file:commit/SKILL.md]]

TypeDescriptionTask Action Words
featNew feature or functionalityImplemented, Added, Created
fixBug fixFixed, Resolved, Corrected
docsDocumentation changes onlyUpdated documentation, Documented
styleCode style (formatting, semicolons, no logic change)Fixed styling, Improved formatting
refactorCode change that neither fixes bug nor adds featureRefactored, Restructured, Improved
perfPerformance improvementOptimized, Improved performance
testAdding or updating testsAdded tests for, Improved test coverage
buildBuild system or external dependenciesUpdated build, Upgraded dependencies
ciCI/CD configuration changesUpdated CI/CD, Configured pipeline
choreOther changes (tooling, configs)Updated, Maintained, Cleaned up
revertRevert a previous commitReverted, Rolled back

Checklist Before Responding

Before showing output, verify:

  • "Summary Task Daily" section is present at the TOP (after date)
  • Tasks are TRANSFORMED (not raw commit messages)
  • Tasks use clear action verbs (Fixed, Implemented, Updated, etc.)
  • Related commits are grouped into single tasks
  • Empty/WIP commits like [] are excluded from tasks

🚫 WRONG OUTPUT (just dumping commits):

📊 Daily Commit Summary
b0b0352 fix(notification-template): update mock Thai name to include month

✅ CORRECT OUTPUT (transformed to tasks):

📋 Daily Commit Summary
Date: Saturday, March 21, 2026

Summary Task Daily
- Fixed notification template to correctly display Thai month names in mock data

If the "Summary Task Daily" section is missing or contains raw commits, the output is WRONG.

平台分布

Codex

33.41%
按下载量换算61

Claude

29.44%
按下载量换算54

Cursor

19.51%
按下载量换算36

Gemini CLI

9.67%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills