Squash multiple commits

I have five small WIP commits on branch feature/ui that should be one logical change for the code review. Squash commits a4b2..HEAD into a single commit with a clear message 'UI: consolidate signup flow — closes UX-88', run the test suite, and push the squashed result to origin/feature/ui using force-with-lease.

Before I squash these five commits into one for review, make it easy for the reviewer: list what each commit contains (files and key diffs), surface any commits that touch migrations or public APIs that should not be squashed, propose a single commit message that includes ticket UX-88 and the high-level change, and flag any tests that might break after squashing.

On branch feature/ui I’ve made five incremental commits. I’m unsure whether to squash into one or leave some history. What’s the practical rule: which commits should stay separate (e.g., add tests, refactor) versus which should be combined before opening the PR, and what’s the least-risk sequence to squash and push without disturbing reviewers already commenting on individual commits?

Across projects I waste time making many tiny commits and then rebasing/squashing before PRs. Where is the friction coming from — my workflow, editor, or team expectations — and what concrete habit change will reduce wasted rebasing while keeping reviewable history? Suggest a default commit-sizing and a checklist to follow before pushing a branch.