unvibe
Review an AI-assisted change with its context
A maintainer follows a parser change from the original decision to the test that covers it.
Start with the issue
A document parser receives invoices with no date. A reviewer needs to understand whether a proposed fallback will leave the field empty or infer a date from elsewhere in the document.
Follow the change
The unvibe example connects the decision to flag missing dates with the affected parser file and a test fixture. The reviewer can see what the test expects and check that it matches the intended behavior.
Where the team benefits
A maintainer can revisit the decision when investigating a later regression. The trace gives them a starting point for reviewing the code and deciding whether the original behavior still fits.