3 ms·

I think CodeRabbit/others do this already? They learn from your code base/previous PRs, then use that in the future. I built a mini PoC of this a few weeks ago

I think CodeRabbit/others do this already? They learn from your code base/previous PRs, then use that in the future. I built a mini PoC of this a few weeks ago as well, out of curiosity

samiahmadkhan 6mo ago
CodeRabbit reviews one PR at a time using context from past PRs. VibeDrift scans the entire codebase at once and compares every file against its directory peers. Different question: not “does this PR look good” but “does this file follow the same patterns as the files sitting next to it.” Also runs fully locally, zero data sent. Curious what your PoC does though.
- _zer0c00l_ 6mo ago
  There is one potential issue with scanning the entire codebase IMHO - if the codebase is old enough, there can be old snippets of code that DON'T correspond to the current preferences anymore. So scanning the last 200 PRs and reading comments is a bit safer maybe. This is what my vibe coded PoC did - it just used GitHub API to go through the last X merged PRs, see the diffs and all discussions and create a document based on that - the developer manifesto kind of, a set of preferences and rules for this dev team. Then, use this manifesto as context whenever reviewing new PRs
  - samiahmadkhan 6mo ago
    [dead]
  - samiahmadkhan 6mo ago
    Never say never, you got it now - https://vibedrift.ai/releases https://vibedrift.ai/releases