pranny · HN

Selfship.ai – Surface and fix isues with your agentic applications 24x7

@MarwanMaherH · X

AI Codereview for Gitlab — 基于大模型(DeepSeek,OpenAI等)的 GitLab 自动代码审查工具；支持钉钉/企业微信/飞书推送消息和生成日报；支持Docker部署；可视化 Dashboard - [查看仓库](https://github.com/sunmh207/AI-Codereview-Gitlab)

@aryawarti_aky · X

Hey Daniel ! I Built PRisk — an AI-powered pull request risk intelligence platform for GitHub & Gitea. Paste a PR URL and get an evidence-backed Merge Confidence Score before you merge. 🔗 I'd love to hear your feedback!

jallmann · HN

> want without a PR process that requires hardware authentication or proof of presence Just curious, what do you use for this? I built OTP Guard [1] a few years ago for exactly this problem, although I haven't seen any alternatives in the space. Does GitHub have something built-in now? The original framing was more "local malware compromising your GitHub account" ... it never occurred to me that the malware could be a LLM. I really should update the page. [1] https://otpguard.com

@jakemoshel · X

Turn issues into sandbox tested PR’s from your current stack

othmanosx · HN

I still don't like the fact that AI is adding more stuff for us to read, it's accelerating the code production but slowing down the code review. I built my own code reviewer as well ( https://pyor.review/ ), surfacing the important stuff first is the right track, but adding more stuff to read is daunting, but asking AI to just point you to what you need to focus on and skim the noise is what I'm leaning more towards.

@hyraxai · X

@polsia · X

You can ship a vibe-coded app by lunch. You can also ship a vibe-reviewed bug by Friday. Pullflow reads the PR nobody else bothered to open.

kellan_strong · Product Hunt

Factory Nexus by TynHub Ai and swarm agents

logphase · HN

I've always struggled to hold a large PR in my head. AI-assisted coding has made it worse. Especially when dozens of files are modified, it became harder to understand what changed: distinguishing important changes from trivial ones and identifying if regressions were introduced. I was also tired of switching between file and method to build the whole picture in my head — I wanted all the context at the point of the function I was reviewing. I guess I'm just more of a visual person. I realized t

@vilfred_sikker · X

free signups!