Skip to main content
pre.dev’s key differentiator: agents cannot mark a task as complete until it passes automated verification. No more “looks good but is broken.”

​
What Gets Verified

Every completed task goes through a verification pipeline before a PR is opened:
For TypeScript/typed projects, the full compilation must pass:
  • No type errors
  • No missing imports
  • Proper interface compliance
  • Strict mode checks (when configured)
Code must pass the project’s linting rules:
  • ESLint, Prettier, or your configured linter
  • Consistent formatting
  • No unused variables or imports
  • Style guide compliance
If the task includes test requirements:
  • All new tests must pass
  • Existing tests must not break
  • Coverage thresholds met (if configured)
For frontend/UI tasks, pre.dev runs visual checks:
  • Components render without errors
  • Layout matches expectations
  • Interactive elements function correctly
  • No console errors in the browser
  • CTA elements redirect properly

​
How It Works

1

Agent Writes Code

The build agent implements the task based on the specification
2

Type Check

Compilation must pass — if it fails, the agent fixes and retries
3

Lint Check

Code style rules must pass — if they fail, the agent fixes and retries
4

Tests

All tests must pass — if they fail, the agent fixes and retries
5

Browser Verification

UI must render correctly — if it fails, the agent fixes and retries
6

PR Opened

All checks passed — a pull request is created with verified, working code
The agent iterates automatically until all checks pass. You only see the final, verified result.

​
Why This Matters

Without acceptance verification, AI-generated code often has:
  • Type errors that surface only at build time
  • Missing imports that break at runtime
  • UI components that render incorrectly
  • Tests that were never actually run
  • Formatting inconsistencies
pre.dev eliminates these by making verification a gate — not an afterthought.

​
Verification in the PR

Each PR shows a verification panel with all acceptance criteria results: 
# Acceptance Verification

CRITERION                                   STATUS
------------------------------------------  ------
Hero renders, CTA redirects to /signup      PASSED
TypeScript compiles, all unit tests pass    PASSED
API < 200ms, error handling user-friendly   PASSED

​
Custom Verification

The verification pipeline adapts to your project:
  • Python projects — mypy/pyright type checking, pytest, flake8/ruff
  • Go projects — go vet, go test, golint
  • Rust projects — cargo check, cargo test, clippy
  • Frontend projects — TypeScript, ESLint, Vitest/Jest, Playwright
Verification rules are detected from your project configuration (tsconfig, eslint config, pytest.ini, etc.) — you don’t need to configure anything manually.