Your Personal Git History Analyst

You spent the whole week coding. You were busy — meetings, debugging, feature work, code reviews. You feel productive. But when you actually look at your git history, you shipped two commits on Monday and three on Thursday. The rest was meetings and Slack threads with a lot of context switching.

The gap between how busy you feel and what you actually shipped is almost always wide. The problem isn’t laziness — it’s invisibility. Your commit history is a data layer that almost nobody reads about themselves. OpenClaw reads it for you and tells you what it means.

What This Solves

The “I’ve been so busy” problem. You feel overwhelmed. Your calendar is full. But are you actually building things? Git history doesn’t lie about what got committed. If your commit frequency has dropped 60% over the past month while your meeting load stayed the same, that’s actionable information — not a guilt trip.

Burnout detection before it hits. Burnout rarely announces itself. You just notice you feel tired, uninspired, or like everything is harder than it used to. Your commit history can show you the slope before you feel the cliff. A gradual decline in commits — especially in evening and weekend work — is a reliable early signal. OpenClaw tracks this and can alert you before the decline becomes a crater.

Focus drift. You intended to spend Q3 on Project A. But the git data tells a different story: 40% of your commits are on Project B, 25% on infrastructure cleanup, and 15% on a side project you started in June. The intention was clear; the execution wasn’t. Git history is an objective record of where your time actually went.

Rhythm awareness. When do you do your best work? Some people are morning commit machines. Others ship their best code after 10pm. Most people have no idea — they’ve never looked. OpenClaw maps your commit timestamps and tells you your natural rhythm, which is useful for scheduling, capacity planning, and protecting your peak hours.

How It Works

Daily Git Log Ingestion

A cron job runs once a day — typically in the evening — and pulls recent commits from your configured repositories. It writes structured data to your log:

## Git Activity — 2026-07-21

**New commits:** 7 across 3 repos
**Projects:** clawspiral (4), dotfiles (2), homelab-ansible (1)
**Commits by hour:** 09:00 (1), 10:30 (2), 14:00 (1), 20:00 (2), 22:30 (1)
**Largest commit:** "Refactor auth middleware" (14 files, 847 lines)
**Merge commits:** 2
**Average commit size:** 6.2 files, ~210 lines changed

**Notable:** First commits on homelab-ansible in 11 days.

This is fully automated. OpenClaw runs git log --since="yesterday" across your tracked repos and parses the output.

Weekly Pattern Analysis

Once a week, OpenClaw reviews your git log and generates a summary:

## Weekly Git Report — July 14–21

**Total commits:** 31 (up from 24 last week)
**Repos worked in:** 6 (same as last week)
**Project breakdown:** clawspiral 45%, homelab-ansible 23%, dotfiles 19%, other 13%
**Commits by day:** Mon 8, Tue 5, Wed 4, Thu 7, Fri 3, Sat 2, Sun 2

**Rhythm observation:** Your most productive window this week was 9–11am. 
  You shipped 40% of your commits before noon. Afternoon commits were 
  mostly small fixes and reviews.

**Trend:** Commit count up 29% week-over-week. The slump in late June 
  appears to be recovering. Morning focus is stronger this week than 
  in any of the past 3 months.

**Risk flag:** None. This was a solid week.

Monthly and Quarterly Reviews

For longer time horizons, OpenClaw can answer questions that require months of context:

“How has my project focus changed over the quarter?”

“July: clawspiral 41%, personal tooling 22%, homelab 18%, open source 12%, other 7%. June: clawspiral 28%, open source 25%, homelab 22%, personal tooling 15%, other 10%. Your clawspiral focus nearly doubled from June to July. Open source contribution dropped by half. If the open source work was intentional, that’s a drift worth examining. If unintentional, your month went somewhere you didn’t send it.”

“Am I working more or less than I was six months ago?”

“Average daily commits: 4.1 now vs 5.8 in January. You’ve dropped ~29% in commit volume over 6 months. But your average commit size has increased from 3.2 files to 6.8 files — fewer but larger commits. You may be batch-working more, or spending more time on each change. Combine with your calendar data: your meeting load in January was 6h/day; it’s now 3.5h/day. Fewer meetings but similar output — possibly more focused work.”

“What does my weekend-to-weekday ratio look like?”

“Weekend commits: 18% of total (slightly above the 15% average for solo developers). Your weekend work is concentrated in the late evening — 78% of weekend commits are after 8pm. Your partner mentioned in March that you work too much on weekends. The data confirms it: Saturday afternoon is your highest-leakage period for weekend work.”

Cross-Referencing with Intent

This is where it gets useful. If you set quarterly goals or track priorities elsewhere, OpenClaw can compare git reality against stated intent:

“Your Q3 goal was: 60% on clawspiral, 20% on homelab, 20% learning. Your Q3 reality so far: 41% clawspiral, 18% homelab, 22% open source, 19% learning. Gap analysis: clawspiral is 19 points below target. Open source is 22 points above. You’re learning more than planned — which isn’t bad, but it means clawspiral is getting squeezed. Do you want to redirect, or update the goal?”

The Setup

1. Configure your repo list — Create a git-repos.md file listing the repositories you want tracked, with full paths. Include both work and personal. More repos = more complete picture.
2. Set a daily cron job — Runs git log --since="yesterday 00:00:00" on each repo and parses the output. Choose a time that won’t interfere with active work — late evening (9–10pm) is usually good.
3. Define your baseline — OpenClaw needs to know what “normal” looks like for you. Run a few weeks before enabling alerts. Tell it your quarterly priorities so it can do the gap analysis.
4. Enable weekly reports — A Sunday evening summary with patterns, trends, and any flags.
5. Optional: integrate with your calendar — If you track meeting load elsewhere, OpenClaw can correlate meeting hours against commit output. Useful for the “I was in meetings all week” defense — or its rebuttal.

Limitations

Git only tracks what’s committed. If you pair-program, pair on tickets someone else commits, or do significant code review without committing yourself, git underrepresents your contribution. This isn’t a productivity metric; it’s a commit metric.

Commit frequency varies by project type. A microservices repo with 50 commits a week is normal. A static site with 3 commits a week is also normal. Context matters. OpenClaw can learn the difference if you give it enough history.

It can surface guilt. Seeing that you shipped 3 commits this week when you felt “so busy” is uncomfortable. The goal isn’t shame — it’s calibration. Feelings are real but sometimes inaccurate. Git data is one input, not the verdict.

Privacy. Your git history is local. OpenClaw reads from your repos; it doesn’t send your code anywhere. If you work on sensitive repos, add them to an exclusion list.

Why This Works

Most knowledge workers have no objective record of what they built. Your calendar shows meetings. Your messages show conversations. Your git history shows what you shipped. That’s a different kind of truth — the kind that shows up in the artifact, not the process.

The real value isn’t the daily log. It’s the six-month trend. When you can see that your commit rhythm follows your sleep, or that every time you take on a new side project your main project’s commits drop by 40%, or that you’ve had two productive weeks followed by a crash every quarter for the past year — those are patterns worth knowing.

OpenClaw makes git history personal. Not for your employer. For you.