Verifying AI Output · ai-skills

Verification and Safe Use · Beginner to Intermediate

5topics
5lessons

Treat every assistant-produced change as unreviewed until a check passes. The checks are ordinary engineering: compile, lint, simulate, assert, test, and compare against a reference.

Verification pipeline for assistant-written changes.

Each stage rejects a different class of defect; a rejection returns to revision.

Lesson	What it covers
The verify-first checklist	A fixed check order and a worked escape count.
Differential testing against a reference	A runnable comparison of a generated function against a reference.
Property-based checks	Invariants that hold for every input, without a full reference model.
Review the diff, not just the result	Reading small diffs line by line, with a runnable RTL check.
When to refuse to trust	Cases where no check is enough, with compound-risk arithmetic.

Check yourself A generated module compiles cleanly. Why is that not enough to trust it?

Compilation checks syntax and types, not intent. Only simulation, assertions, and comparison against a reference check what it does.

Up nextThe Verify-First Checklist

Practice this lesson Report an error