站会。每天早上。『你昨天做了什么？』
And me, every morning, staring at the ceiling trying to reconstruct my own day. I shipped stuff! There were commits! I just couldn’t tell you what they were without opening four different tools.
So I built the tool I wanted: DevTrack.
→ GitHub: github.com/sp1128/DevTrack
What it does #
DevTrack is a local CLI that hooks into Claude Code and quietly records your dev activity as you work:
- Sessions and active coding time
- Files changed (Claude’s edits plus git working-tree changes)
- The important commands you ran — tests, builds, installs — with secrets scrubbed out
- Git commits: branch, message, files touched, lines added/removed
- Tasks, inferred from Claude’s task tools or from your commits
Then it answers the standup question directly:
npm install -g devtrack
devtrack init
claude # work like normal — DevTrack records in the background
devtrack today # what did I actually do today?There are week and month views, a Markdown weekly report you can paste anywhere (with an optional AI summary), and an activity heatmap for when you want to feel something about your own consistency.
The part I care about most #
Everything stays on your machine. No account, no cloud sync, no analytics. Your dev history is yours. DevTrack doesn’t modify the Claude Code client either — it just listens to the hooks Claude Code already exposes.
When I demo’d it for the video, it showed my day back to me: 19 active minutes in the test session, 3 files, 2 commits, 4 commands — including the build that failed. Especially the build that failed. That’s the stuff I always forget by the next morning, and it’s exactly what a standup is supposed to surface.
Try it #
It’s MIT-licensed and on npm. If you live in Claude Code and your standups sound like mine, give it a spin — issues and PRs welcome.
The video version of this post is on my TikTok: @dormroomdev.