@gabrielcdev · X

github notifications on discord DM

@ReleasePilotHQ · X

Just shipped ReleasePilot. Connect GitHub → push code → release notes write themselves. No Actions. No config. Just push. Free for 1 repo & free trial → #buildinpublic #indiehacker #saas #github

@manixh · X

@patchlight_dev · X

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.

@manoj_surya_ · X

I just launched 🚀 A Proof of Ship, every day — straight from your GitHub. You already do the hard part: you commit. git-to-x turns that into a designed card and posts it to X every morning. Your timeline finally looks like what you actually are — someone who ships. → 8 card designs, rotating (terminal, heatmap, flame, ticker…) so it never gets stale → weekly + monthly milestone cards — your streak becomes a story worth following → tweet from your CLI / Cursor / Claude Code without leaving your editor → free for 10 days, full access See who else is shipping daily under #proofofship — and join them. It touches your repo, so safe-to-try came first: → open source (AGPL) — audit it or self-host → read-only — we never touch your code This is my first build-in-public tool. I built it for myself, and for anyone tired of switching between shipping and posting about shipping. First 100 get founding lifetime — a permanent number on every card. Try it, tell me

@JessePeplinski · X

👋 I’m building live on Twitch using Codex & Claude. Pop in any time. Let’s connect!

@david_kubgak · X

Generate a professional README from any GitHub repository in seconds.

u/Thick-Rip-1187 · Reddit

i started realizing something weird about github profiles you can look at someone's github and see commits, stars, repos, languages, all that stuff. but you still don't really know what that person is actually good at. like... someone could have 500 commits because they're building AI infra. someone else could have 500 commits because they're building dev tools. on the surface, their profiles can look pretty similar. and i kept thinking... why is it so hard to understand what s

@outagedeck · X

OutageDeck, outage alerts for 168 cloud vendors (AWS, Cloudflare, OpenAI, Slack), built only on their official status feeds. No crowd reports, no scraping, no false positives. Free email alerts for 5 providers + a free JSON API, no key.

Koimiao · V2EX

做了个小工具，可以从各个维度评估一个 GitHub 项目，想请大家拍砖 找开源项目时，我们常常会先看 Star 、README 和最近一次提交。如果你是独立开发者，正在维护自己的开源项目，也想知道怎么让自己项目更健康、被更多人看见，第一步该从哪里做起？ 所以最近我做了一个小项目：TrustOSS http://trustoss.org 输入一个 GitHub 仓库链接，TrustOSS 会把这些公开信号整理成一份可读的仓库健康报告：活跃度、维护情况、社区、文档与成熟度评分；也可以进一步查看漏洞、CI 、真实依赖者、维护者集中度和 Star 异常情况。 想要评估一个开源项目，或者维护自己的开源项目，想知道短板在哪里，都可以直接试试（是免费的！

@nathanghart · X

Submitting for approval. I built a free tool for anyone about to ship a vibecoded app. It scans your repo for what bites you in prod (leaked keys, no auth, no error handling). I ran it on 1,868 AI-built apps and even caught my own scanner being ~42% wrong.