The insight: all the information is already in Git. Commits, PRs, authors, timestamps. It's just unreadable for anyone who isn't a developer.
So I built an AI layer on top that:
1. Connects to GitHub/GitLab/Bitbucket via OAuth (reads only metadata, never code) 2. Captures commits and PRs in real-time via webhooks 3. Uses Claude to transform raw Git activity into human-readable summaries 4. Delivers automatically via email or Slack on whatever schedule you want
Example transformation:
Before: "fix: rm deprecated api calls, refactor: extract auth middleware"
After: "Fixed API timeouts by updating deprecated endpoints. Improved
security by centralizing authentication logic."
Some things I learned building this:
- Commit messages follow strict patterns (73% start with feat:/fix:/refactor:) but contain almost no "why" context - Teams spend ~78 hours/year/person writing status reports manually - The question "what did we ship this week?" accounts for 62% of queries about repositories
Other features that emerged from the same data layer: - AI agents you can chat with ("What did Sarah work on last week?") - Developer leaderboards with contribution scoring - Auto-generated public changelogs
Free tier: 1 repo, 1 automation. Pro ($15/mo): 5 repos. Enterprise ($49/mo): 20 repos + custom branded reports.
Happy to answer technical questions about the architecture, AI prompting strategy, or webhook handling. Also curious - how do other teams handle the "what did we ship" problem?
I've been building Gitmore for a while now. The problem I was solving: every week I'd spend 1-2 hours scrolling through commits trying to piece together "what did we ship?" for stakeholders who don't want to read "feat: impl oauth2 w/ refresh".The insight: all the information is already in Git. Commits, PRs, authors, timestamps. It's just unreadable for anyone who isn't a developer.So I...
Hey HN, I built Gitmore because I was tired of spending hours every week copy-pasting from git log to write status updates. The problem: Git history contains everything about what your team shipped, but extracting useful information from it is painful. Commit messages are written for machines, not stakeholders. Status reports are a time sink. Changelogs go stale. And developers doing critical...
Like many devs, I got tired of bouncing between repos just to answer simple questions like:What actually changed this week?Which PRs are stuck?What did we ship?Who’s waiting on a review?It sits on top of your GitHub/GitLab/Bitbucket repos and turns the noise into something readable.The hardest part by far? Webhooks. Each provider sends totally different payloads:different keysdifferent...
Something that always bugged me as a developer is how different Git platforms are when it comes to their event data. Commits, PRs, merge events… none of them agree on anything.So I ended up building a small project with a friend to solve that problem for ourselves — a unified activity layer that takes raw Git events and turns them into something consistent and actually useful.The worst part:...
Got tired of spending Friday afternoons scrolling through commits to write status reports, so I built something to automate it.The problem: Git history contains everything about what your team shipped, but it's buried under cryptic messages like "feat: impl oauth w/ refresh tokens" that stakeholders can't understand.What I made: A tool that monitors repos and generates readable summaries...