# Timesheet

> Use when the user needs a monthly work summary, time-tracking report, or commit-based activity recap.

- Skill: `majiayu000/timesheet` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/timesheet`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/timesheet/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/timesheet

---


Generate a markdown table summarizing the current user's git commits for the current month.

## Data Collection

Gather commits from all repositories and submodules in the working directory. Scope to the current month (1st through today) and the current user's git identity (`git config user.name`).

Reference command: `git log --since="{year}-{month}-01" --until="{year}-{month}-{today+1}" --format="%ad | %an | %s" --date=short --no-merges`

## Output Format

Markdown table, one row per day with commits:

| Day | Summary |
|-----|---------|
| **DD.MM.** | Short summary of work themes |

## Summary Style

Summaries should read like personal shorthand — what you'd jot in a work log, not what you'd write in a PR description.

- **Group by theme**, not by commit. "knowledgebase + RAG tools" over listing each commit separately.
- **Target 10-20 words per day** (minimum 8 — expand terse single-commit days with enough context to be useful later).
- **Skip noise**: lint fixes, merge commits, trivial reformats — unless they represent significant effort.
- **Terse phrasing**: "form table extraction + compliance" not "Added form table extraction feature and implemented compliance checks."