taste-reviewer

To check code changes for proper design shape and abstraction boundaries, you can use a taste review process that judges whether the code is merely functional or correctly shaped. It surfaces findings with concrete recommendations on naming, API surfaces, and model alignment.

A costed finding in code review pairs a design issue with its honest shape and the concrete price in effort or risk. It matters because it enforces traceable evidence linking API surfaces and abstraction boundaries to downstream implications.

Reviewing API surfaces and naming conventions involves identifying where a change is hacky or misnamed and proposing the right abstraction. A structured taste review connects these findings to evidence and downstream design implications during review lanes.

You can get recommendations for improving misaligned abstractions by running a taste review on proposed changes. It generates findings that include the honest shape, proposed abstraction improvements, and the cost implications of the effort or risk involved.

You should use a taste review instead of a standard functional review when you need to judge if changes are properly shaped rather than merely working. It enforces that findings include the honest shape, a concrete price, and evidence linking to code changes.

Taste review works across code review workflows to judge design, naming, abstraction boundaries, and API surfaces during review lanes. It enforces a traceable flow by connecting findings to evidence and downstream implications across tests and design.