Release Sanity
Instant risk signal for every pull request
What it does
Release Sanity analyzes pull request diffs and posts an instant release risk check directly on the PR. A single structured comment shows a risk level (HIGH / MEDIUM / LOW), highlights risky areas like auth, APIs, billing, migrations, and deploy config, and generates a release-readiness checklist. The comment updates as the PR changes so teams can quickly sanity-check a release before merging.
Does the same job
all alternatives →- DODepsGuard – One command to harden NPM/pnpm/yarn/bun/uv configsJun 2026 · github.com · ▲40
I kept seeing every npm/pnpm/yarn/bun/uv supply chain post end with the same advice (set a minimum release age, turn off install scripts), and while I know cooldowns are "controversial", they do work. But even if you convince people that they should set cooldowns, it seems many don't end up following through, not sure why, maybe because it means hand-editing five config files in five formats with five different time units, or perhaps the "it won't happen to me" syndrome (or "I'll do it later, it seems complicated" where it's actually very simple). So I created a tool that…
- SPSmart Pull Request Alerts → Faster Code Reviews2025 · pullnotifier.com · ▲13
Like many devs, we lived in Slack hell—random notifications, chaotic threads and PRs always getting missed! We tried everything: Slack bots, GitHub settings, follow-up msgs—nothing worked. So we built PullNotifier. PullNotifier ensures that every PR gets the attention it deserves. It makes sure the right people see them at the right time—without spamming everyone (so you don't have to send those awkward PR request msgs). What makes it different? One notification per PR: No more drowning in redundant messages. Smart routing: PRs go only to the relevant channels or reviewers. Instant…
- IBI built a tool to assist AI agents to know when a PR is good to goJan 2026 · dsifry.github.io · ▲45
I've been using Claude Code heavily, and kept hitting the same issue: the agent would push changes, respond to reviews, wait for CI... but never really know when it was done. It would poll CI in loops. Miss actionable comments buried among 15 CodeRabbit suggestions. Or declare victory while threads were still unresolved. The core problem: no deterministic way for an agent to know a PR is ready to merge. So I built gtg (Good To Go). One command, one answer: $ gtg 123 OK PR #123: READY CI: success (5/5 passed) Threads: 3/3 resolved It aggregates CI status, classifies review comments…
- GPGitGuard - Painless GitHub PR Automations2025 · gitguard.dev · ▲12
Hey HN, Every team I've been on has cobbled together some sort of combination of GitHub branch protections and custom scripts to make sure that PRs conform to organization policies and best practices. Things like: - When {X} file is changed, require review from team {Y} - When a new db migration is added, ensure that a special set of tests pass - Require multiple approvals when the PR is very large - Add a special label to PRs that include breaking changes - Allow emergencies / hotfixes to break glass and bypass all of the above Most teams tend to start out with a little script running…
More dev tools this month
the category →
The first open-source price index for GPU compute
Dev tools · 10d ago · getcomputable.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
Launched alongside, March 2026
the whole month →
Switch from ChatGPT to Claude with import memory feature
AI · Mar 2026 · claude.com
