shadcn-errors-cli-sync-mismatch

What problem does it solve?

This skill prevents the shadcn CLI from silently wiping your local changes when you re-run shadcn add with overwrite, especially when upstream components change and you need to recover customizations safely.

Core Features & Use Cases

• Diff-first overwrite workflow: Use --dry-run and --diff to preview exactly what the CLI will change before any destructive write.
• Choose the right sync strategy: Apply one of three approaches—vendor snapshot, diff-merge, or fork—to match how much you customized and how frequently upstream changes.
• Preserve customizations safely: Move custom variants and extensions into *-extensions.tsx so re-adds and migrations do not delete them, and maintain clear documentation for each component’s sync policy.
• Migration and hygiene guardrails: Run migrations like migrate icons and migrate radix with clean git state to avoid tangled diffs you can’t confidently resolve.

Quick Start

First make your git working tree clean, then run pnpm dlx shadcn@latest add <component> --diff to review the upstream changes before applying overwrite.