... enrolled repos with auto-review Runtime Watchdog GitHub Action One application per account, and we manually review each one, so send us the project you actually maintain. Apply here https://app.looksgoodtomeow.in/d... Thanks again to everyone who checked LGTM out on launch day. Would love to see this running on some real OSS projects. Reply here if you have questions about scope, license criteria, or anything else. Tarin ...

... merges, it s Wednesday. The flow state is dead. The joy is gone. We built this product because we were tired of that story. We believe the "Review Blocking Queue" is the single greatest enemy of developer happiness. The "LGTM" Trap For the last decade, we ve treated Code Review as a necessary evil. We accepted that to have quality, we had to sacrifice speed. We forced our most senior engineers to spend 40% of their week acting as human ... ... spellcheckers. They scroll through diffs, hunting for missing semicolons or unused imports, their eyes glazing over. The result? The "LGTM

... treated the AI as a safe sandbox where they could mess up, learn, and fix it before the "adults" came in. By the time the Senior Engineer saw the PR, the code was clean. The Senior said, "Nice work, LGTM." That little endorphin hit of validation was all the engineer needed to keep shipping. We often talk about "10x Engineers." But you can't be a 10x Engineer if you're paralyzed by the fear of being a "1x Imposter ...

... long time now. Comment from Ron Cohen(@roncohen): @steveb if you have smaller commits/pull-requests which trunk-based development favors, you can argue you ll have more, but smaller reviews. I think that s a good thing though. Big PR = LGTM while a smaller PR often has more detailed comments. I don t think I can see how there needs to be more team communication with TBD? Comment from Alex Gap(@lagap): At @Product Hunt , we're closer to the trunk ...