Alternatives
Products that do what Stoney does
Know when your code drifts from the original requirement
- 1IM
0github.com is a pull request viewer that color-codes every diff line/token by how much human attention it probably needs. Unlike PR-review bots, we try to flag not just by "is it a bug?" but by "is it worth a second look?" (examples: hard-coded secret, weird crypto mode, gnarly logic, ugly code). To try it, replace github.com with 0github.com in any pull-request URL. Under the hood, we split the PR into individual files, and for each file, we ask an LLM to annotate each line with a data structure that we parse into a colored heatmap. Examples:…
Oct 2025 · 0github.com
- 2
- 3
- 4
- 5AC
We needed something like --dangerously-skip-permissions that doesn’t nuke your untracked files, exfiltrate your keys, or install malware. Claude Code's permission system is allow-or-deny per tool, but that doesn’t really scale. Deleting some files is fine sometimes. And git checkout is sometimes not fine. Even when you curate permissions, 200 IQ Opus can find a way around it. Maintaining a deny list is a fool's errand. nah is a PreToolUse hook that classifies every tool call by what it actually does, using a deterministic classifier that runs in milliseconds. It maps commands to action types…
Mar 2026 · github.com
- 6
- 7IB
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…
Jan 2026 · dsifry.github.io
- 8IB
I built a GitHub app that detects it in pull requests, notifies or blocks them. Alongside it, I published a Semgrep ruleset for any stage of the CI/CD. I started this after getting frustrated by all the FUD around malicious code - lots of noise, little effort to solve it. Having said that, it's still a major attack vector - a stored RCE, with the codebase itself as the sink. Feedback is appreciated. The app, PRevent - https://github.com/apiiro/PRevent The ruleset: https://github.com/apiiro/malicious-code-ruleset The research:…
2025 · github.com
- 9ZS
Hi HN, I’m Tobi. For a couple of hours over the past few days I’ve been hacking on something to fix a pain point in my dev workflow: writing status updates. Progress is invisible by default. GitHub, Linear, Jira all track tickets and code, but they don’t do a good job of capturing the narrative between “ticket started” and “ticket done.” You start working on a feature, your PM asks “how’s it going?”, and even though you know exactly how it’s going - because you’ve been committing and making progress - you still struggle to answer. That usually means breaking your flow to piece together an…
2025 · zyg.sh
- 10
- 11CS
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds…
Feb 2026 · docs.continue.dev
- 12
- 13IB
Hi there, The app basically offers a handy user interface on top of Google's PageSpeed Insights API. It allows you to analyze URLs in bulk and save the reports for later references. Also, you can regenerate the saved reports for fresh results. I called this functionality "Automatic Checklists." The app offers "Manual Checklists", too. Those are exhaustive checklists with items in the form of "tasks". The idea is for those tasks to model real-life JIRA tickets, which will be very useful for interns and junior developers. As a start, there are two manual checklists, "Front-End Checklist" and…
2022 · buhalbu.com
- 14DM
Hi HN, In most codebases I’ve worked on, temporary hacks (“TODO: remove later”, “just for this release”) slowly become permanent. Nobody remembers why they exist, but they keep shipping to production. I built a small CLI called DebtBomb to make that explicit. Instead of free-form TODOs, you attach an expiry date to temporary code. When the date passes, CI fails until the code is removed or the expiry is intentionally extended. Recently I added integrations so expired debt bombs don’t just fail CI — they become visible and owned: When a debt bomb expires, DebtBomb can automatically create a…
Jan 2026 · github.com
- 15
- 16
- 17
- 18
Production readiness checker for vibe coders
Jun 2026 · auditme.will-tech.site
- 19OS
Hey Everyone! Avi and I (in the current YC S25 Batch) noticed how fragmented crypto compliance is with rules changing constantly, vary by region, and force developers and legal teams into a scramble. So we hacked together a prototype framework that generates a “guardrail” smart contract which: - Hooks into your KYC provider - Enforces rules defined a simple compliance.yaml file - Automatically blocks users you can't legally serve When regulations shift (new blocked country, updated KYC threshold, etc.), just update your YAML and redeploy with no smart contract rewrites. Audit prep also…
2025 · github.com
- 20IC
Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…
2025 · shadowgit.com
- 21JG
- 22
- 23BS
Hey everyone! Every reviewer loves smaller pull requests, but they can be hard to do practically. We created a Github integration that adds the following features - Commit checkpoints (i.e. stacked reviews) - Autogenerated tabs (based on dependency graphs) - A central pull request inbox (highlights which PRs need your attention) Commit checkpoints helps authors stack smaller changes within a single pull request without having to manage tons of branch offshoots. It works by using the common “[x/n]” prefix notation (where x is the stack number). This is the workflow: - Author makes some…
2023 · backprop.io
- 24IB
Hi HN, When I was in FAANG, I despised ticketing. I was always the eng that refused to update. Then when I was a tech lead, I had the pain of pinging everyone for updates because they hated it too. Things would go out of date, and then no one would really know if we were on track. We also had little visibility into what the team was doing outside of pinging/standups. So I made an AI that looks at every commit you push and updates tickets for you. It can create tickets if there isn't one, update, leave comments, tag associated commits etc... Basically, it's an "AI Board Babysitter" so…
2025 · usevectra.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →