Dev tools · alternatives · 2026
24 alternatives to Stoney
Know when your code drifts from the original requirement
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
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 · its alternatives →
- 2
Preflight▲77Hey HN, I’m a product designer on a payments team. Every time we were close to shipping a feature, we’d run a bug bash in a giant Google doc or spreadsheet: copy the spec in, write the test cases, ask people to mark Pass/Fail, paste screenshots, then manually turn everything into Jira tickets. It worked, but it always felt a bit painful. Instead of another heavy test management tool, I wanted something that feels closer to the tools we actually like using. More Linear/Notion, less old-school QA. With Preflight, you paste your product requirements and Figma link and get an initial…
Dec 2025 · preflightqa.xyz · its alternatives →
- 3
GitQuest▲187Hey HN, I built Git Quest, it reads your public GitHub history and turns it into an idle RPG character. How it works: - Your most-used language determines your class (TypeScript → Paladin, Python → Sage, etc.) - Commits generate Power and XP - Your character auto-battles dungeons while you code – no active play needed - Enemies drop loot across 5 rarity tiers - Live leaderboard ranks developers It only reads public GitHub data. I built it because I wanted something that rewards coding consistency without being another "streak" tracker. The idle mechanic means prolific coders naturally…
2025 · gitquest.dev · its alternatives →
- 4
Keeping your Jira issues safe from secrets
2022 · marketplace.atlassian.com · its alternatives →
- 5
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 · its alternatives →
- 6
Drift score for any GitHub repo
Aug 2026 · drift.reweaver.ai · its alternatives →
- 7
Support teams handle hundreds of tickets but rarely analyze them systematically. Patterns like workarounds, feature confusion, or rising escalations often surface too late. This tool: Analyzes Zendesk tickets daily (last 7 days vs 30-day baseline) Detects workaround language, expectation gaps, and escalation trends Sends Slack alerts when thresholds spike Includes real customer quotes for context Built with TypeScript, Vercel, Supabase, Slack SDK, and Claude for extraction and categorization. Free for now. Would love feedback from support leaders or B2B builders.
Feb 2026 · usercall.co · its alternatives →
- 8
Patra▲57Manage Jira with natural language commands right from Slack. Create, update, and track tickets effortlessly without leaving your workspace.
2025 · patra.app · its alternatives →
- 9IB
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 · its alternatives →
- 10
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 · its alternatives →
- 11ZS
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 · its alternatives →
- 12
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 · its alternatives →
- 13
- 14
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 · its alternatives →
- 15
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 · its alternatives →
- 16
Your team's code review rules, enforced on every PR
May 2026 · cross-check.dev · its alternatives →
- 17
Kinlyze▲10Know what breaks when a developer leaves - on autopilot
Jul 2026 · kinlyze.com · its alternatives →
- 18
ShadowGit▲20Hey 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 · its alternatives →
- 19
- 20
Production readiness checker for vibe coders
Jun 2026 · auditme.will-tech.site · its alternatives →
- 21
Recall▲16One developer solves it. Every developer knows it.
Feb 2026 · recall.team · its alternatives →
- 22
Regtrace▲5Catch LLM quality drift before your users do
Jun 2026 · regtrace-docs.vercel.app · its alternatives →
- 23
Howdy friends. I've been a zero to one product manager for 12 plus years and along the way I kept borrowing pieces from different discovery frameworks until I had a methodology of my own, one that actually raises the odds of an idea succeeding. This does not replace user interviews obviously, but it leads you in the right direction. Looking forward for your feedback
Jul 2026 · github.com · its alternatives →
- 24
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 · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →