AI code review tools excel at analyzing syntax within a single file or a pull request. They can catch a missing semicolon a mile away. But they suffer from the same blindness as a rushed human reviewer: they review the diff, not the intent.

They overlook the original prompt used by the coding agent and fail to grasp the broader business context of the application.

Code review - whether conducted by a human or an LLM - doesn't actually verify whether the code accomplishes what was prompted. It cannot confirm that the code aligns with its intended spec, or that the agent's claim of "task completed" is checked in a deterministic way. LLMs notoriously defer hard, multi-step, or dependent tasks, which means that the intent itself has diverged by the time the PR is opened.

If we want to trust AI code in production, we have to stop verifying the diff and start verifying the claim.

Has anyone found a reliable way to bind the original Jira ticket / GitHub issue to the actual code change in CI? I've been working on solving this problem with Shipmoor.dev, but I'd love to hear how other teams are tackling the "intent gap."

Status page is green (at time of writing 11:22 UTC)

There was an incident declared earlier today but this says resolved: https://status.claude.com/incidents/lhqp09kxq7pb

Outages today/yesterday were discussed in https://news.ycombinator.com/item?id=49066591 https://news.ycombinator.com/item?id=49056194

Now incident declared: https://status.claude.com/incidents/mfdtrknpxghq

I built Startup Graveyard after realizing it's hard to find startups that didn't make it.

You can paste your startup idea, and it will find similar startups that were shut down or abandoned, along with why they failed (when that information is available).

I'd love to hear what the HN community thinks:)

I've been running production Laravel apps for a while and noticed that most teams have zero monitoring on their cron jobs and queue workers. Uptime monitors check if a URL responds 200, but they can't tell you if your scheduler stopped firing or your workers crashed.

I built Crontinel (https://crontinel.com) to solve this for myself. It hooks into framework events and monitors scheduler health, worker status, queue depth, and agent runs. Open source, MIT licensed, SDKs for Laravel, Node, Python, Go, Rust, PHP.

Curious what others here use. Do you monitor your cron/queues? What tools? How did you find out when something broke?