EfimovSD
Joined 4 years ago
Karma
1
Submissions
5
Member since
Jun 19
Recent submissions
Comment · 7 months ago
Comment · 10 months ago
Yes, “structural conscience” is a great way to put it. We aims to catch locally sensible agent changes that don’t fit the repo’s global patterns and surface them as a PR comment + status check.
If you’re open to it, I’d love to demo it — you can request one on the site. And if you have an agent workflow we could hook into (Copilot/Cursor/Claude + CI), tell me what you’re using and we can explore an integration.
Comment · 10 months ago
Hi HN! I’m the maker of Revieko — a GitHub App that highlights architecture drift hotspots in pull requests and posts the results where reviews happen.
What you get in each PR:
- a PR comment with the top hotspots and file/line pointers
- a status check
— a full report - markdown/ json
How it works (high level): after install it builds a baseline from the repo, then compares each PR to highlight structural changes that are unusual for that codebase
What it isn’t: not a linter, not a security scanner — the goal is “signal for review”, not more noise.
It’s free right now while we learn. I’d love feedback on 2 things: 1. what would make a hotspot truly actionable in your repo? 2. what would be noise that you’d want filtered out?
Install: https://github.com/apps/revieko-architecture-drift-radar Sample output: https://synqra.tech/revieko#modal-sample
App: https://github.com/marketplace/revieko-architecture-drift-ra...
Article on the topic: https://zenodo.org/records/17820299