invoice-generator

Invoice Generator — Tribletext Daily Summary

This skill reads git commits across all repositories in the workspace and produces a concise daily work summary formatted for pasting into Tribletext.no.

Why this exists

Writing daily time reports is tedious. Git commits already capture what was done — this skill turns them into human-readable summaries grouped by day, ready to paste into Tribletext without editing.

How it works

Step 1: Discover all git repositories

Find all git repos under the current working directory. Repos are identified by having a .git directory. Typically this means checking immediate subdirectories:

for dir in */; do
  if [ -d "$dir/.git" ]; then
    echo "$dir"
  fi
done

Step 2: Collect commits for yesterday and today

For each discovered repo, fetch commits authored by the current git user for yesterday and today:

git log --author="$(git config user.name)" \
  --since="YYYY-MM-DD" --until="YYYY-MM-DD" \
  --pretty=format:"%ad | %s" --date=short

• Use the actual calendar dates (not relative dates like --since=yesterday) to avoid timezone ambiguity.
• Collect from ALL repos and tag each commit with which repo it came from so you can group related work.

Step 3: Summarize into 4 lines per day

This is the core value of the skill. Raw commits are too granular — the user needs a high-level summary.

Rules for summarizing:

1. Group by feature/area, not by repo. If frontend and backend commits both relate to "Voyage Schedule search", combine them into one line.
2. Exactly 4 lines per day. No more, no less. If there's less work, make lines more detailed. If there's more work, combine related items.
3. Each line should be a complete thought — describe what was built/fixed/improved, not individual commits.
4. Use action verbs — "Built", "Developed", "Added", "Fixed", "Created", "Implemented", "Enhanced".
5. Include both frontend and backend context when a feature spans both — e.g., "Built Profile page — frontend hook, RTK endpoints, route wiring (GET/PUT /api/profile)"
6. Mention key technical details that help the user remember what they did — endpoint names, component names, patterns used (TDD, RBAC, etc.)
7. Exclude knowledge-base / documentation work. Do NOT include wiki ingestion, knowledge-base maintenance, note-taking, or documentation-summarizing activity in the invoice — only report actual product work (code commits, CRM/Dataverse changes, deployments, bug fixes). The invoice covers billable engineering work, not internal note-keeping.

What NOT to include (always skip):

• Wiki / knowledge-base ingestion or scaffolding (e.g. "ingested N docs", "touched N wiki pages", "scaffolded wiki structure", building an Obsidian/RAG vault).
• Summarizing, cataloging, or indexing source documents into a knowledge base.
• log.md entries whose {type} is ingest, scaffold (wiki), synthesis, or lint — these describe knowledge-base upkeep, not product work.

If a day contains ONLY knowledge-base work and no real commits/CRM changes, say so plainly rather than dressing the documentation work up as billable engineering.

Step 4: Format the output

Present the summary in this format:

**Yesterday (DD Mon):**
- Line 1
- Line 2
- Line 3
- Line 4

**Today (DD Mon):**
- Line 1
- Line 2
- Line 3
- Line 4

Each line should be concise but informative — aim for 10-20 words per line. The user will paste this directly into Tribletext.no, so keep it clean and professional.

Customization

If the user asks for a different number of lines, different date range, or different format — adapt accordingly. The 4-line format is the default, not a hard rule.

If the user specifies a date range (e.g., "this week", "last 3 days"), adjust the git log date filters accordingly. Always convert relative dates to absolute dates for the git commands.