Show HN: Release-gate – a CLI that checks AI-agent PRs for risky changes
I built this after noticing that AI-agent PRs are hard to review. I’m mainly looking for feedback on whether PR-scoped gating is useful, and where the static analysis is still too noisy.
- ▪I built this after noticing that AI-agent PRs are hard to review.
- ▪I’m mainly looking for feedback on whether PR-scoped gating is useful, and where the static analysis is still too noisy.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,405 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=49067759 |
| Publication time | Mon, 27 Jul 2026 11:01:39 +0000 |
| Retrieval time | 2026-07-27T11:12:28.078Z |
| Last seen | 2026-07-27T11:12:33.308Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Y4MU2Nxw9x97 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I built this after noticing that AI-agent PRs are hard to review. There are many tools available but it does not show the reason why the code can be problematic in case of agent.A normal diff can show code changes, but it may not make it obvious that a prompt changed, a model changed, a tool config changed, or model output now reaches an eval/exec path.release-gate is a Python CLI that compares a PR branch against a base ref and reports only what the PR introduced.Example:pip install release-gate release-gate pr --base origin/mainIt can also create a lockfile for prompts/model/tool config:release-gate lock . release-gate audit . --lockThis is early. I’m mainly looking for feedback on whether PR-scoped gating is useful, and where the static analysis is still too noisy.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.