3 ms·
This is a really interesting approach to the “ADR amnesia” problem. What I like most is that you’re inserting context at the moment of change (PR time) instead
by poor_hustler 8mo ago
This is a really interesting approach to the “ADR amnesia” problem.
What I like most is that you’re inserting context at the moment of change (PR time) instead of relying on people to proactively search docs. That’s where most documentation systems fail — they require memory and initiative.
One question I have: how do you prevent this from becoming noisy over time? In my experience, the biggest risk with automated PR comments is that teams start ignoring them once the signal-to-noise ratio drops.
- iamalizaidi 8mo agoReally appreciate that — that’s exactly the gap I was trying to address. Re: noise — I agree, that’s the main failure mode for any PR bot. A few things I did to keep signal high: Only trigger on explicit file patterns (no fuzzy matching by default) Idempotent comments — it updates instead of spamming new ones If multiple decisions match, it groups them into a single comment Severity levels (info / warning / critical) so teams can tune strictness Optional “fail critical” mode so it never blocks PRs unless configured The goal is that it behaves more like a linter than a chatbot — predictable and quiet unless something clearly matches. If it ever becomes background noise, it’s failed
- verdverm 8mo agoComment rings are against HN posting guidelines, please inform your friends / users