$ ernest inspect .
ernest v0.1
Verdict: Needs attention
Diff: 3 files changed main..HEAD
Findings: 1 issue(s) · [medium] retry guard lacks coverage
Verification plan: cargo test -p billing
Ship code with proof not vibes.
Ernest inspects pull requests like a senior reviewer: repo rules, behavior drift, tests, CI, and hidden risk before merge.
You are on the list. We will reach out when your beta invite is ready.
No spam. Private beta invites.
Meet @Ernest where review happens.
Ernest should be easy to call for help from
Open
Fix billing retry guard
# support
Customer-facing incidents
Thomas Today at 4:41 PM
@Ernest is PR #1284 safe to merge for the billing incident?
1 reply
Ernest APP Today at 4:41 PM
Not yet. I found one medium finding in src/payments/retry.rs: the new retry branch can skip the idempotency guard.
Verified: cargo test -p billing passed, but the guard path still needs coverage before deploy.
Frequently Asked Questions
What does Ernest review?
Ernest inspects the harness around a change: repo rules, changed behavior, tests, CI config, commands, and evidence. It focuses on actionable risk instead of style noise.
Does Ernest replace human reviewers?
No. Ernest prepares the evidence and highlights hidden risk so reviewers can spend their time on judgment, architecture, and product tradeoffs.
How fast is the inspection loop?
Ernest is built on Rust and runs close to your repo, so the first pass stays fast enough to fit into the pull request loop instead of becoming another queue.
When can my team get access?
Join the waitlist and we will invite private beta teams in batches while we tune the review workflows with early users.
⚠️ 1 finding
📁 3 changed files
⚠️ Medium finding
Retry guard can be skipped
The new retry branch can bypass the idempotency guard when the first charge attempt times out.
src/payments/retry.rs:84▸ Review focus (2)
▸ Policy sources
☺