See what changed and why.
Trace changes across AI codebases and give reviewers the context behind the code.
Trace a change in a document parser
In this sample, a reviewer investigating an AI-assisted parser change needs to see why the code changed, where it changed, and which check covers the new behavior.
Intent
Handle invoices that omit a date so they can be flagged for review.
Code change
A change in
parser/date.pyreturns an empty date and a review flag when the source omits the field.Verification
A linked test fixture checks that a missing date triggers a review flag and leaves the date empty.
Where unvibe fits
Code review
Follow the change from its stated intent to the affected files and related checks.
Regression investigation
Find the changes and decisions associated with a behavior that shifted.
Team handoffs
Give maintainers the context to understand why earlier decisions were made.