Skip to main content
Generaldvcrn

daily-commits

Summarize a person's git commits for a specific date, grouped by feature points, in English. Use when reviewing daily work output.

Stars
15
Source
dvcrn/openclaw-skills-marketplace
Updated
2026-05-29
Slug
dvcrn--openclaw-skills-marketplace--daily-commits
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/dvcrn/openclaw-skills-marketplace/HEAD/plugins/andrew020--daily-commits/skills/daily-commits/SKILL.md -o .claude/skills/daily-commits.md

Drops the SKILL.md into .claude/skills/daily-commits.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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
  1. 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
  1. 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
  2. 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