← ClaudeAtlas

time-registrationlisted

Summarize recent git work for time registration. Use when the user asks what they worked on, needs a time log, wants a work summary, asks about today's/yesterday's/last week's work, or invokes /time-registration:time-registration. Accepts an optional time period argument (defaults to today).
rvanbaalen/skills · ★ 0 · Code & Development · score 61
Install: claude install-skill rvanbaalen/skills
# Time Registration Summarize recent git activity into a short, comma-separated one-liner suitable for time registration or standup notes. Includes commits from sibling worktrees of the current repo, remote-tracking branches (work pushed from other machines), and recently merged PRs — not just the current working tree. ## Arguments The user may provide a time period as a free-text argument: - "today" (default if nothing specified) - "yesterday", "this week", "last week", "last 3 days", "monday", "since friday", etc. Parse the intent and translate it to a `git log --since`/`--until` date range. Before running the log, echo the accepted hints so the user sees their options: ``` Time period: today (default). Other options: yesterday, this-week, last-week, last-3-days, since-<day>. ``` If the user passed an argument, skip the hint line and just confirm the parsed range (e.g. `Time period: last week (2026-04-13 → 2026-04-20)`). ## Process ### 1. Determine the date range Convert the user's input to concrete dates. Examples: - "today" → `--since="today 00:00"` (default when no argument given) - "yesterday" → `--since="yesterday 00:00" --until="today 00:00"` - "last 3 days" → `--since="3 days ago"` - "this week" → `--since="last monday"` - "last week" → `--since="2 mondays ago" --until="last monday"` ### 2. Sync with remote Work may have been pushed from other machines or already merged upstream — fetch before scanning so remote-tracking refs are current. Run once per uni