git-daily-work-report
npx skills add https://github.com/wangdengyue/git-daily-work-report --skill git-daily-work-report
Agent 安装分布
Skill 文档
Git Daily Work Report
Automatic daily work report generation by scanning Git repositories.
When to Use
Use this skill when:
- User asks to generate a daily report from git commits
- User wants to summarize work done on a specific date
- User requests work summary based on code changes in a monorepo or multi-repo project
- User needs to check commits by a specific author
Workflow
Step 1: Scan Git Repositories
Use the bundled script to scan all git repositories under a root directory:
python scripts/get_git_log.py <root_path> <date> [--author <name>] [--json]
Parameters:
root_path: Root directory containing multiple git repositoriesdate: Date inYYYY-MM-DDformat--author(optional): Filter commits by author name--json: Output in JSON format for LLM processing (default: formatted report)
Example:
# Scan all repos for commits on a specific date
python scripts/get_git_log.py /path/to/project 2026-01-23
# Filter by author
python scripts/get_git_log.py /path/to/project 2026-01-23 --author "dengyue"
# Output JSON for LLM processing
python scripts/get_git_log.py /path/to/project 2026-01-23 --json
Note: The script automatically scans all subdirectories and finds git repositories. It’s designed for monorepo layouts where multiple projects exist under a single root directory (e.g., D:\work\ containing projects like Libraries, core, Admin, etc.).
Step 2: Analyze Commits with LLM
Process the git log output to generate work summary:
- Group commits by repository/project
- Summarize what was changed based on commit messages and file changes
- Identify major features, bug fixes, or improvements
- Generate clear, professional work content description
Step 3: Submit Report (via MCP)
Use browser automation MCP to submit the generated work content to the internal reporting system.
Output Format
The script generates a formatted report by default:
dengyue æäº¤æ¥æ¥ï¼2026-01-23ï¼
==========================================
[Libraries]
- è¿æ¥redisçslave
æä»¶åæ´ï¼
M src/redis/connection.py
[Admin]
- ä¿®å¤ç¨æ·ç»å½bug
æä»¶åæ´ï¼
M controllers/auth.go
M models/user.go
For LLM processing, use --json to get structured data. The final work summary should be:
- Clear and concise: Describe what work was done
- Categorized: Group related changes by repository
- Professional: Use appropriate language for daily reporting
Example final output format:
## 2026-01-23 工使»ç»
### EMLibraries
- ä¿®æ¹ Redis è¿æ¥é
ç½®ï¼åæ¢å° slave èç¹ä»¥å®ç°è¯»åå离
### Admin
- ä¿®å¤ç¨æ·ç»å½æ¶ç session éªè¯ bug
- ä¼åç¨æ·ä¿¡æ¯æ¥è¯¢æ§è½
### Bug ä¿®å¤
- è§£å³ç»å½è¶
æ¶é®é¢
- ä¿®å¤æééªè¯é»è¾é误
### 代ç ä¼å
- éæ Redis è¿æ¥æ± 管ç
Notes
- Ensure git is installed and accessible in the system PATH
- The script sets UTF-8 encoding for output on Windows platforms automatically
- The script handles UTF-8 encoding for commit messages (with error tolerance)
- File changes are included for each commit to provide context
- The script skips nested git repositories (only scans top-level repos)
- For projects with many repositories, the scan may take some time