Every commit, PR, and push gets normalized into a standard schema – message, description, author, timestamp, files changed, PR context. The AI reasons over structured data, not just raw text.
PR descriptions carry more context than commit messages. We capture both.
Automated reports:
Schedule weekly or monthly summaries to Slack or email. Forward to investors, share with your board, or just stay in the loop.
Other features:
- Slack bot: Team can ask questions without GitHub access
- Contributor stats
Security:
Webhooks only. Git platforms push event metadata to us – we never pull or clone.
Good point on commit message quality.
We've addressed this partly by design, every event gets normalized into a standard schema: message, description, author, timestamp, files changed, PR state.
The AI reasons over structured data, not just raw commit messages. PR descriptions especially help. Most devs write oneline commits but actually explain context in the PR body. We capture that.
Still, teams with good commit hygiene get better output. No way around it.
I haven't said that the app is fully vibe coded, i said we used AI. The app is not fully vibecoded but we have used AI assistance and i am aware of the security concerns that comes with github/ slack implementation. Its a question of how you use AI in your app the system is fully designed by us so we know how it exactly behaves and how the data and tokens are stored/ exchanged.
Of course i haven't asked every dev that exists whether they use AI or not but most companies/devs does, you choose to not use it, good luck with that.
We have deifinitely used AI just like everyone else, but we are senior 4+ years of experience. Also Gitmore doesn't have the ability to read your code nor execute or write. We only get data from webhooks which are commits/ PR info with no code. Thanks for your Attention.
Gitmore uses github api and AI generates insights/ custom newsletters for users.
You can also connect Gitmore's AI into slack and ask it questions directly from your workspace.