Failure explanations
Each failing test explained in plain language against the code that changed.
Phase 2 · coming next
Robit reads the diff, test results, changed-file coverage, and the plain Markdown scenarios in .robit/. It explains failures, ranks gaps, drafts the test plan, and leaves the final call on what ships to your reviewers.
npm i @robit-one/reporterLive todayCoverage reporting and the dashboard.NextThe pull request agent.
Why it failed
services/refund.ts:88 now returns closed after a partial capture. Two refund tests still expect shipped.
Top gap
Test plan · from .robit/specs/Checkout.md
The product line
01
A transcript, a ticket, a sketch, a half-formed idea. Robit refines whatever you have into an implementation-ready spec.
02
A ready spec becomes a pull request, built and tested against a coverage goal before it opens.
03
Every PR is checked against your tests and knowledge. A person signs off, and verified behavior becomes your source of truth.
The standard
100% coverage isn't a goal. It's the gate.
When tests cost almost nothing, "good enough" stops being a tradeoff. It's a choice not to look. We believe every pull request should meet 100%, and that every exception should be written down, with a name on it. That's the standard Robit is built toward.
90% is good enough
10% of a 10k-line service is 1,000 lines running in production with no verification. Name which 1,000.
Tests are too expensive to write
Not anymore. An agent writes them as fast as the code. Incident response is the expensive part.
Phase 2 · how the agent decides
Plain Markdown scenarios in .robit/ sit beside the code. On every pull request the agent reads them with the evidence your CI already produces, and hands a person the decision.
Evidence in
Robit review
Reads the change against the specExplains, ranks, prompts, plans, and flags drift. Proposes; never merges..robit/
robit.md # guide + scope
specs/
Checkout.md
Refunds.mdHuman decision
A reviewer approves the plan and chooses what shipsOnly steps a person promotes become part of .robit/.No .robit/ folder yet? The agent still runs on the diff, tests, and coverage. The spec grows as reviewers promote steps.
One agent · six outputs
Understand
What happened in this pull request?
Each failing test explained in plain language against the code that changed.
Changed files ranked by severity, linked to the uncovered lines and functions.
Act
What should the reviewer do next?
A scoped prompt per gap, ready to paste into Claude Code, Codex, or Cursor.
A checklist built from the diff and your .robit/ scenarios. Reviewers edit it.
Learn
What should the repository remember?
Scenarios in .robit/ that this change may have made inaccurate.
Manual steps with no matching end-to-end test, ordered by value.
One pull request · #2418 · 09:14 → 09:44
01Available today
The reporter sends results and coverage from the CI you already run. The project average looks healthy. The lines this pull request changed do not.
416 / 418 · 1m 42s
checkout/refund.test.ts › partial refund leaves order shipped
checkout/refund.test.ts › refund total never exceeds capture
The average hides the risk. Robit measures the diff.
02Coming next
The agent will explain each failure against the diff, rank the uncovered changed lines, and put the ones behind core scenarios first, each with a scoped fix prompt.
Two of these back steps your team marked core — flows that must never break, written down once in .robit/. Those rank first, automatically.
03Coming next
Coverage says the code ran, not that it is right. A reviewer steps through the drafted plan, edits it, and marks each step.
Manual test plan · #2418@dana · 2 of 3 pass
Step 1 fails by hand, too. The fix goes in before merge.
04Coming next
The reviewer promotes the step that caught the bug. It is committed to the branch, credited to them, and every future pull request is checked against it.
421 / 421 · 1m 51s · changed files 94%
.robit/specs/Checkout.md +1 core step
Promoted by @dana
.robit/specs/Checkout.md ## Refunds - [core] Refund total never exceeds the captured amount. + - [core] Partial refund leaves the order shipped, not closed.
Human in the loop
Promote to spec?
Partial refund leaves the order shipped, not closed.
What you can use now
Available today
Coming next · Phase 2
Install the reporter now and your history is already in place when the agent arrives.
What it costs you to try
Vitest, Playwright, Jest, Mocha, or Deno, and the tests you have.
No second runner or webhook to host.
One per project, revocable any time.
Anything that sets standard CI variables.
// vitest.config.ts
import { defineConfig } from 'vitest/config'
import { RobitReporter } from '@robit-one/reporter/vitest'
export default defineConfig({
test: {
reporters: [
'default',
new RobitReporter({
token: process.env.ROBIT_TOKEN,
suite: 'unit',
}),
],
},
})// playwright.config.ts
import { defineConfig } from '@playwright/test'
export default defineConfig({
reporter: [
['list'],
['@robit-one/reporter/playwright', {
token: process.env.ROBIT_TOKEN,
suite: 'e2e',
}],
],
})// jest.config.js
module.exports = {
reporters: [
'default',
['@robit-one/reporter/jest', {
token: process.env.ROBIT_TOKEN,
suite: 'unit',
}],
],
}// .mocharc.cjs
module.exports = {
reporter: '@robit-one/reporter/mocha',
'reporter-option': [
`token=${process.env.ROBIT_TOKEN}`,
'suite=unit',
],
}
# pass reporter as the package string; mocha won't accept a required class# wraps deno test, collects coverage, posts the run
deno run -A jsr:@robit-one/reporter/run --suite=unit -- src/
# or read the token from the CI environment
ROBIT_TOKEN=rbt_xxx deno run -A jsr:@robit-one/reporter/run --suite=unit -- src/Questions
No. Robit reads the results your existing suites already produce. One import in your config, one line of options. If you remove it, your tests run exactly as they did before.
Test names, pass/fail/skip counts, durations, and the coverage summary your runner emits. Branch, commit and environment come from CI variables. Source code is not uploaded by the reporter.
On its own, no — it means every line ran. That is the point of pairing it with .robit/ specs: coverage proves the code executed, the specs say which behaviour a human still has to confirm.
Only when a person promotes a step. When the agent ships, promoted steps will be committed to the pull request branch and credited to the reviewer who approved them. Nothing is written to .robit/ without that approval.
Free to try. No infra to run. Works in your CI today.
npm i @robit-one/reporter