1 pointby slmslm229 hours ago2 comments

vinkupa8 hours ago
Smart approach but, is the trade off worth it? Most code reviewers provide enough information in PR comments - see coderabbit, turingmind AI, greptile etc this adds slim value on top of that must have tooling layer
- slmslm227 hours ago
  Code review tools are for engineers in the PR workflow. Gitmore is for people who never open GitHub, founders reporting to investors, PMs writing changelogs, stakeholders who want visibility without learning Git. If everyone on your team can read GitHub, you're right slim value. If you're constantly translating Git activity for non-technical people, that's the use case.
philipwhiuk9 hours ago
> Would you trade code-level analytics for ~~better security~~ reduced privacy
Some probably would. I think many likely write commits that are insufficiently detailed to really capture the scope of the change.
> Stack: - Token encryption: Fernet (HMAC-SHA256 + AES-128-CBC) - Webhook verification: Timing-safe HMAC-SHA256 - 2FA: TOTP + backup codes
This isn't really your stack but sure.
- slmslm228 hours ago
  Most commit messages are useless. PR descriptions are hit or miss. We do what we can structured schema, patterns, aggregation. But if a team doesn't document their work, no tool fixes that.
  And yeah, "stack" was wrong. That's security implementation. Next.js, MongoDB, Claude is the actual stack.