$ 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
Ernest should be easy to call for help from
$ 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
-50% exclusive launch offer
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.
No. Ernest prepares the evidence and highlights hidden risk so reviewers can spend their time on judgment, architecture, and product tradeoffs.
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.
Start with GitHub from this page, install Ernest on your organization, then enable the repositories you want Ernest to inspect.
⚠️ 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
☺