timesheet

Summarize monthly Git commits into a Markdown work report.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill timesheet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timesheet
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/timesheet
Command: npx skills add https://github.com/JHostalek/dotclaude --skill timesheet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns a user's scattered monthly Git commits into a concise work summary, avoiding manual review of commit history and reducing noise from routine changes.

Core Features & Use Cases

  • Monthly Commit Reporting: Collects the current user's commits from the first day of the month through today.
  • Focused Attribution: Filters commits using the configured Git username and excludes merge commits from the report.
  • Theme-Based Summaries: Groups related commits into concise daily work themes rather than listing every individual change.
  • Use Case: Use it at the end of each month to create a personal timesheet from repository activity for status updates, retrospectives, or administrative reporting.

Quick Start

Ask the timesheet skill to generate a Markdown summary of your current month's Git work.

Frequently Asked Questions about timesheet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a monthly work report from Git commit history?

To generate a monthly work report from Git commit history, the Skill filters your repository commits by your configured Git username, excludes merge commits, and groups the results into daily work themes. It outputs a Markdown summary covering the current month through today.

Can I create a personal activity recap from repository commits without listing every individual change?

You can create a personal activity recap by grouping related repository commits into concise daily work themes rather than listing every individual change. This reduces noise from routine changes and provides a clear, theme-based summary for retrospectives.

Does the monthly timesheet report exclude merge commits from the summary?

Yes, the monthly timesheet report explicitly excludes merge commits from the summary. It filters the repository history to only include commits attributed to your configured Git username, ensuring the report reflects actual development work.

What do I need to configure to summarize my current month's Git commits?

To summarize your current month's Git commits, you need to configure your Git username so the tool can filter the repository history accurately. It then collects commits from the first day of the current month through today to build the report.

What is the best way to turn scattered Git commits into a clear timesheet for status reporting?

The best way to turn scattered Git commits into a clear timesheet for status reporting is to group repository activity by day and work theme while excluding merge commits. This avoids manual review of commit history and produces a concise Markdown summary of your monthly activity.