For builders who ship

TURN YOUR
GIT COMMITS INTO
SHAREABLE CONTENT
WORTH POSTING.

Git Recap watches the repos you choose, pulls commit history on-device, and generates a clean daily, weekly, or monthly update you can share on X, LinkedIn, or anywhere else builders post progress.

Local-firstBYOK AImacOS + Windows
How Git Recap works
3 steps
01
Paste example posts

Optional, but useful when you want Git Recap to learn your voice from a few past tweets or posts.

02
Add your API key

Use your own OpenAI or Anthropic key. Git Recap supports both right now.

03
Pick a repo and generate

Git Recap turns today's commit messages into a post you can edit, copy, and publish.

Local git history in, post-ready draft out.

How it works

The app stays out of your way until you want to summarize what you shipped.

Step 1

Watch the repos you care about

Add the folders that contain your projects. Git Recap will scan and watch those repos locally.

Step 2

Pull in commits for any period

Daily, weekly, monthly, or yearly recaps can use stored local activity plus fresh git history from watched repos.

Step 3

Generate and export your update

Use OpenAI or Anthropic with your own key, then export a polished image card for your social post.

Your voice, your recap

Paste a few writing samples, add some output notes, and let Git Recap shape the draft around how you naturally post. The same git history can sound very different depending on the voice you want.

Casual / build-in-public

Write a short build-in-public update. Keep it casual and conversational, like a tweet thread. Focus on what I shipped and what I learned, not technical jargon.

Output

Okay today was a solid day. Pushed the repo watcher to finally handle edge cases I'd been ignoring. Also reworked the landing page copy, much tighter now. Still a lot to do but the app is starting to feel real. 🔨

Professional / LinkedIn

Summarise today's engineering work as a professional LinkedIn update. Use confident, first-person language. Highlight outcomes and business value, not just the technical details.

Output

Today I advanced two key areas of the product: hardened the local repository watcher to handle previously untested edge cases, and rewrote the core landing page to sharpen the value proposition. Both moves directly improve reliability for end users and conversion for new visitors.

Technical / developer audience

Write a concise technical summary for a developer audience. Include specific changes, the reasoning behind them, and any interesting implementation details worth sharing.

Output

Fixed a chokidar race condition where rapid .git/FETCH_HEAD writes triggered duplicate events. Debounce was 500ms but the watcher was re-attaching on every reload. Moved init to a singleton. Also refactored the landing page component tree to reduce prop drilling through three layout levels.

Built for builders who post progress

Day-by-day build threads work best when the recap is fast to write and still specific. Git Recap gives you a factual starting point from your actual git history instead of a blank page.

That means fewer vague updates, less context-switching, and a tighter loop between shipping work and sharing it publicly.

Privacy first

  • Repos are chosen by you and watched locally.
  • Commit messages never leave the device unless you generate an AI summary.
  • Signing in syncs aggregated activity, not your full codebase.

Git Recap Lifetime Access

One payment. No subscription. Keep the app forever.

Lifetime access

Buy once, own forever.

Buy Git Recap once with a one-time payment and keep every future update.

  • Lifetime access to the app
  • All future updates included
  • Unlimited local git tracking
  • Unlimited AI recap generation (BYOK)
  • Shareable recap exports
Price
$5one-time

One-time payment. Lifetime access.

Purchase is attached to your signed-in account.

Not satisfied? View the return policy

FAQ

Does Git Recap read my source code?

No. It reads git metadata from the repos you choose to watch, such as commit hashes, branches, timestamps, and commit messages.

Do my commits stay local?

Yes. Commit history stays on-device unless you explicitly generate an AI summary with your own provider key or sign in to sync aggregated activity.

Do I need an account?

No. The desktop app works locally without an account. You only need an account if you want synced activity or to buy lifetime access.

Which platforms are supported?

macOS and Windows are supported today. Linux support is planned.

How does pricing work?

Git Recap has one paid option: lifetime access for $5. Buy it once and keep the app forever.

Git Recap summarizes git activity from the repos you choose to watch. Review generated copy before posting it publicly, especially if your commit messages contain sensitive information.