ImpactGate: A merge gate that scores the structural decay AI adds
sagenschneider
36 points
47 comments
September 16, 2026
Related Discussions
Found 5 related stories in 78.2ms across 6,833 title embeddings via pgvector HNSW
- How to Build an AI Software Factory: Agents That Open, Review, and Merge PRs makaimc · 29 pts · September 11, 2026 · 51% similar
- AgentsDock: An IDE designed for agentic AI research ZihuiGeorgia · 32 pts · September 12, 2026 · 46% similar
- How we monitor internal coding agents for misalignment lukaspetersson · 47 pts · September 06, 2026 · 45% similar
- Transitions.dev: UI transitions for AI agents eustoria · 23 pts · September 14, 2026 · 45% similar
- Prime Gaps at Most 186 simonpure · 49 pts · September 03, 2026 · 45% similar
Discussion Highlights (11 comments)
appleappleapple
Nice idea. Our new CTO brought in a tool he made for analyzing cyclomatic complexity and it’s been useful since we’re a heavily AI-forward shop. BTW, you can avoid your comments being flagged and killed by writing them yourself! I know it’s tempting to offshore it to AI (especially after you’ve vibe-coded a whole project) but some genuine human communication goes a long way.
VladVladikoff
The overuse of “gate” in this post title makes me think the entire thing was vibe coded even the marketing.
owebmaster
A sloppy project to find slop in projects. It sure works well
philipwhiuk
Interesting idea even for non-AI code.
MichaelNolan
Maybe I missed it, but it look like this has just a single metric. Maybe instead of making a new project, you could try to get this metric added to a existing tool like https://dekobon.github.io/big-code-analysis/index.html which already has dozens of metrics.
samayashar
Great way of detecting AI slop. Claude is pretty good at adding focused changes and if a fix is already present, then it correctly points it out rather than adding unnecessary refactors.
EliasWatson
What languages does this support? I'm guessing it's Python only, but it would be nice if that was mentioned somewhere.
Retr0id
What's the structural decay score of this HN title? Apparently not high enough to be gated.
WD-42
Kind of ironic that this thing purports to “gate” slop, yet the entire project is slop, including the README and even the authors comments here. I hate this timeline.
Lerc
What score do we get for a group of fixes to single line bugs that are obvious once spotted? There is an implication that all AI changes add complexity and reduce quality, but it is obvious that the quality and complexity is a property of the code not the writer, so all equivalent changes should be equal no matter what the shource. How do clear improvements to make something simpler yet more functional score under this system?
altcognito
Isn't this just static code analysis? We have tools for this.