agentleFS
JHostalekJHostalek/dotclaude/skills/timesheet/SKILL.md

timesheet

Skill11 starsChanged 4 months agoCC0-1.0View on GitHub

Prepare monthly timesheet entries from Git commits.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write like personal shorthand — work-log note, not PR description.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate a markdown table of the current user's git commits for the requested month, defaulting to the current month.

Data Collection

Repo in working directory. Scope: requested month, defaulting to the current month (1st → now), current user only — filter by git config user.name.

Use local calendar boundaries: midnight on the first day of the requested month through the current time, or the next month’s midnight for a completed month. Calculate dates with calendar-aware arithmetic. Filter the author name literally and exclude merge commits; never construct an invalid date by incrementing the day number.

Output Format

Markdown table, one row per day with commits:

DaySummary
DD.MM.Short summary of work themes

Summary Style

Write like personal shorthand — work-log note, not PR description.

  • Group by theme, not by commit. "knowledgebase + RAG tools" over listing each commit separately.
  • Target 10-20 words per day (minimum 8, retaining useful context).
  • 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."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.