OpenSkillIndex← back to search
claude-code

Dotclaude timesheet

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

install
source · Clone the upstream repo
git clone https://github.com/JHostalek/dotclaude
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/JHostalek/dotclaude "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/timesheet" ~/.claude/skills/jhostalek-dotclaude-timesheet && rm -rf "$T"
manifest: skills/timesheet/SKILL.md
source content

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:

DaySummary
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."