sync-shadcn

Plans, reviews, and tracks upstream shadcn docs changes for merging into Plate docs.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill sync-shadcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-shadcn
Source: https://github.com/udecode/plate/tree/main/.agents/skills/sync-shadcn
Command: npx skills add https://github.com/udecode/plate --skill sync-shadcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plate's docs app is a forked product surface of the shadcn docs architecture, and keeping it aligned with upstream shadcn changes requires tedious manual diffing, classification, and decision tracking. This Skill automates the audit of upstream commits, inventories every added, modified, or deleted change, and produces reviewable merge plans so nothing is silently missed.

Core Features & Use Cases

  • Range Planning and Inventory: Compares the tracked baseline commit against the current upstream target, classifies each change as adopt, smart-merge, fork, defer, or exclude, and writes a reviewable plan under docs/sync/shadcn.
  • Status, Review, and Dashboard Commands: Provides status checkpoints, freshness review audits against the current checkout, and a generated HTML dashboard for visually deciding each delta row.
  • Micro-Overlap Direct Merges: Applies qualifying tiny upstream fixes to already-synced Plate components directly during planning, while stopping for user review on all substantive slices.
  • Use Case: After shadcn ships new docs changes, run a scoped lane such as sync-shadcn command-menu to get a plan with screenshots, owner files, and recommended merge slices before touching apps/www.

Quick Start

Ask the assistant to run sync-shadcn status to see the current baseline, pending upstream changes, and the recommended next sync step.

Frequently Asked Questions about sync-shadcn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync shadcn docs changes into Plate?

Run sync-shadcn to compare the tracked baseline commit with the current upstream target in ../shadcn/apps/v4. It writes a reviewable plan under docs/sync/shadcn, applies qualifying micro-overlap fixes directly, and stops for your review before any substantive apps/www changes.

How do I check the current shadcn sync status?

Run sync-shadcn status to see the baseline commit, planned target, landed partial syncs, reviewable differences, and deferred decisions. Status mode only reads status.json and upstream refs; it never patches apps/www or writes run artifacts.

Can I sync only one feature instead of the full range?

Yes, pass a scope such as sync-shadcn command-menu to run a scoped planning lane that inventories only changes affecting that surface. Scoped plans cannot advance lastSyncedCommit alone; the full-range lane remains pending for out-of-scope rows.

Does sync-shadcn modify Plate code automatically?

Only for micro-overlap merges: tiny single-file fixes on already-synced components with no product judgment needed. All other implementation requires you to explicitly accept a plan and slice in a later instruction after reviewing the written plan.

What is the sync-shadcn dashboard used for?

The dashboard command generates a static HTML decision board from docs/sync/shadcn/deltas.json, grouping deltas by product surface with states like pending, defer, fork, rejected, and synced. You mark rows in the browser, copy the generated apply payload, and send it back to apply decisions.

Why does sync-shadcn review report a stale plan?

Review reports stale-upstream when origin/main has newer apps/v4 commits than lastPlannedCommit, stale-local when Plate owner files drifted, or stale-status when status.json contradicts the plan. A fresh verdict means the existing plan can still be implemented safely.