I measured my context switching by scanning Git commits
Git-based context switching tracker, but time estimates rely on unvalidated research assumptions.
Turn each git push into a product update
Local git hooks mean zero repo access, unlike GitHub-native commit tools.
Engineering teams, solo developers who need to communicate progress
GitWit · Commitizen · GitClear
This is a local CLI that translates every push into product updates.
They're logged on Debrief (link is available on repo), but you can ostensibly change it to wherever.
I built this as a first-step to helping engineers communicate work real-time. I'm aware many companies have built-in pipelines, but was hoping that this could bridge the gap between what was planned and what was done (e.g. the trade-offs and granular decisions made).
Hope some folks find it useful! -Will
BTW - you can use `local` mode on this, so that you run a script on every push to summarize with your own AI scripts, in case you need anything bespoke.
Git-based context switching tracker, but time estimates rely on unvalidated research assumptions.
AI-summarized commits for standups, but Geekbot and Standuply already do this.
Commits as force graphs over time. Hypnotic but missing actual insights: why branches diverge, merge velocity.
Free terminal agent with git undo and permission gates versus Claude Code's $20 monthly subscription.
Hunk-level splitting beats git add -p for messy working trees.
2MB Rust binary replaces 100MB Node.js alternative; extensive LLM provider coverage with fallback support.