shadcn-errors-cli-sync-mismatch

To prevent shadcn CLI from overwriting your custom edits, enforce a clean git status and use `add --dry-run` and `add --diff` to preview upstream changes before applying `--overwrite`.

The best way to update shadcn components without losing local variants is to move custom extensions into `*-extensions.tsx` files, ensuring re-adds and migrations do not delete your customizations.

Running shadcn add with overwrite breaks custom UI components because the CLI silently wipes local changes when upstream components change, requiring diff-merge or fork strategies to recover customizations safely.

Yes, you can preview shadcn CLI changes by running `pnpm dlx shadcn@latest add <component> --diff` to review exact upstream modifications before executing any destructive write operations.

Choose between vendor snapshot, diff-merge, or fork strategies for shadcn component migrations based on how much you customized the component and how frequently the upstream changes occur.

Yes, you need a clean git working tree before running shadcn migrations like `migrate icons` or `migrate radix` to avoid tangled diffs you cannot confidently resolve during component updates.