Agent skill
timesheet
Use when the user needs a monthly work summary, time-tracking report, or commit-based activity recap.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/timesheet
SKILL.md
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."
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?