Developer work journal · Git + Stepper
CommitDiary explains what you built, fixed, refactored, tested, and shipped without making you rewrite your commit history by hand.
Works from your Git workflow. Local-first. Sync when authenticated.
feat(auth): add token refresh handlingtodayfix(api): handle failed webhook retriestodayrefactor(ui): split dashboard widgetstodaytest(sync): add queue retry coveragetodayDaily engineering update
Today’s work improved authentication, webhook recovery, and dashboard maintainability.
The app is more resilient when sessions expire or callbacks fail.
What is CommitDiary?
CommitDiary is a developer work journal that turns Git history into clear, human-readable engineering reports for standups, sprint reviews, retrospectives, release notes, and portfolios.
The missing context
At the end of a busy day, the hard part is not finding the commit hash. It is explaining the work clearly to yourself and everyone around you.
The context is scattered across commits, so the update sounds smaller than the work.
Product leads need progress, risk, and testing context, not a list of file changes.
Refactors, tests, infrastructure, and cleanup matter even when they do not look like features.
Git already records the effort. It rarely turns that history into something easy to learn from.
From code to communication
CommitDiary sits above Git. It turns low-level activity into a useful memory of the work without asking you to maintain another journal.
CommitDiary starts with the Git history your work already creates.
The extension finds your commits, changed files, categories, and affected components.
Authenticated sync unlocks reports, dashboards, badges, and team visibility.
Stepper routes the AI job, handles failures, and validates a predictable report.
Bring the result to standups, reviews, Discord, release notes, or your portfolio.
The reliability engine
Stepper powers CommitDiary’s AI report generation. It sends each job to a configured provider, handles the rough edges, and returns a predictable report your workflow can use.
Explore Stepper on GitHubReport job accepted
Provider selected by config
Response normalized
Seven report fields passed
Callback completed
Built for the work around the code
From one developer tracking a week of work to a team preparing a sprint review, CommitDiary keeps the source familiar and the output readable.
For your own work
Keep a useful record of what you built, fixed, tested, and improved across repositories.
For team communication
Turn implementation details into updates that engineering and product teams can both read.
For real workflows
Local storage, queued sync, report backfills, and Stepper keep the workflow dependable.
Report anatomy
Every AI report follows a clear structure, so it can move from the dashboard to Discord, a shared link, or your next meeting.
The change in one line
What happened and why
Specific work completed
The reason behind it
Risk and coverage
What follows
Searchable context
Report templates
A standup needs a different shape from a sprint review. CommitDiary keeps the facts and changes the frame.
Improved API sync reliability and added retry coverage for failed queue jobs.
Next: test repository report generation and confirm webhook retry behavior.
This week focused on sync reliability, report generation, and dashboard visibility.
The system is better prepared for unstable networks and delayed AI callbacks.
The repository reporting flow moved closer to production readiness.
Work covered commit discovery, Stepper jobs, dashboard states, and Discord notifications.
Separated dashboard components and moved sync handling into focused modules.
The codebase is easier to maintain and future report changes should be safer.
A week in context
12 commits summarized this week
A readable layer above Git
CommitDiary does not replace Git, code review, or engineering judgment. It makes the history they create easier to understand.
| The question | Raw Git log | CommitDiary |
|---|---|---|
| What happened? | Commit messages and files | A plain-language work summary |
| Why did it matter? | Manual interpretation | Rationale and likely impact |
| What needs attention? | Not shown | Testing areas and next steps |
| Can I share it? | Copy and rewrite | Ready for updates, links, and Discord |
| Can a non-engineer read it? | Usually difficult | Designed for shared understanding |
Developer trust
CommitDiary never uploads the whole repository. It keeps a local journal, then authenticated cloud reporting sends commit metadata and bounded evidence made from diff statistics and sampled patch excerpts.
Read how CommitDiary handles dataYour journal begins in the editor.
Work can wait safely until you reconnect.
Cloud features require a signed-in connection.
Reports support judgment; they do not replace it.
Made for where work gets explained
Walk in with a clear update, not a rushed scan of yesterday’s commits.
Explain progress, impact, and the work that still needs attention.
Give product and engineering teams one readable view of delivery.
See patterns in fixes, tests, technical debt, and delivery flow.
Share a real work history through reports and activity badges.
Summarize contributor work, releases, fixes, and repository progress.
New developers
Experienced developers
Product and engineering teams
Start with your next commit
Install CommitDiary in VS Code, create your account, connect with an API key, and let your work journal build from there.
Questions, answered plainly
CommitDiary is a developer work journal. It turns Git activity into clear reports that explain what you worked on, what changed, and why it may matter.
The VS Code extension discovers your commits and keeps a local journal. Authenticated sync can send commit metadata and bounded diff evidence to generate reports, dashboards, badges, and notifications.
No. Authenticated cloud reporting sends commit metadata, file paths, diff statistics, and sampled patch excerpts within a fixed size limit—not the whole repository.
Stepper is the reliability engine behind AI reports. It handles provider routing, retries, rate limits, failover, validation, callbacks, and structured output.
Stepper is provider-flexible. The active AI provider depends on the deployment configuration, so CommitDiary is not tied to one vendor.
Yes. Commit discovery and local storage work in your editor. Unsynced work can wait in a local queue until you reconnect.
Yes. Its structured reports can be shaped into standups, weekly updates, sprint reviews, technical debt reports, release notes, and portfolio summaries.
No. CommitDiary summarizes engineering activity. It does not replace code review, testing, product context, or engineering judgment.
CommitDiary in one paragraph
CommitDiary turns commits, changed files, categories, components, and diff summaries into clear reports for standups, weekly updates, sprint reviews, retrospectives, release notes, Discord notifications, and public activity badges. Stepper handles provider routing, retries, validation, failover, callbacks, and structured AI output.
Your work is already in Git
Install the extension and turn your next commit into a useful engineering update.