akhnid
Joined 10 months ago
Karma
5
Submissions
38
Member since
Dec 22
Recent submissions
Comment · 10 months ago
Thanks for the feedback, basically the agent you can ask it anything. As for the newsletters they are custom so you can set your own prompt.
Comment · 10 months ago
How it works:
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.
We store: - Commit messages, PR titles, descriptions, timestamps, authors, file counts
We never access: - Source code, diffs, file contents
Stack: - Token encryption: Fernet (HMAC-SHA256 + AES-128-CBC) - Webhook verification: HMAC-SHA256 - 2FA support
Check your repo's webhook settings after connecting to verify.
Free for 1 repo: https://gitmore.io
Comment · 10 months ago
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.
Appreciate the thoughtful take.