Guides · Nov 12, 2026
How to review AI UI changes before you merge
Use a finding, its screenshot and a focused code diff to decide which AI-suggested UI changes to approve.
Review an AI-suggested UI change by matching it to the original finding and screenshot, inspecting the code diff, and checking the updated page before you merge. Xpensiv produces a fix list from your public page. You or your coding tool make the edits, and you decide which changes ship.
Start with a finding you can see in the screenshot. Read what is wrong, where it is and what it should be. For example, the existing Xpensiv guide uses a Buy button contrast target of 4.5:1 as a specific instruction to give your AI tool. Use the finding's own instruction for your page.
Ask the coding tool to make that edit in a branch. Compare the diff with the request. If you asked for a button-label change, check whether the diff also changes layout, shared components or other copy. Ask the tool to explain those edits before deciding whether to keep them.
Open the updated public page at desktop and phone width. Compare the affected element with the original screenshot, then re-run the check. Read the new findings to see whether the original problem remains and whether the edited page has other reported problems.
Approve and merge only the changes you have reviewed. Xpensiv does not push commits to your repository. The approval step happens in your own development workflow, where you can inspect the diff and choose what to apply.
Product details: /you-approve-every-change · /blog/fix-list-not-rewrite · /how-it-fits-your-workflow