Retroactive UIFork (git history → browsable versions)

Why this exists

UIFork is usually forward-looking: you fork components to explore new ideas before promoting one. This skill covers the retroactive case: the work already landed as a sequence of commits on a branch, and you want that history to be navigable in the running app—same route, same props, same data—by flipping versions in the UIFork widget instead of reading git log, raw diffs, or checking out each commit.

Use it when you need design or eng review of how a UI evolved, stack-ranking polish steps, or a walkthrough of a feature branch as it was built—not when you are only sketching new variants from scratch (use the UIFork tooling and agent skill below on its own).

What you get: each chosen commit (plus an optional baseline at BASE) becomes a real file snapshot (git show <ref>:path) wired into *.versions.ts with labels derived from commit subjects, so the timeline is browsable and labeled, not a pile of opaque v3 ids.

Implementation details (CLI, ForkedComponent, watch server) still follow UIFork upstream; this document is the git + curation + snapshotting workflow on top.

Companion — UIFork agent skill (optional)

This retroactive workflow assumes you can look up UIFork CLI usage, init layout, and app wiring. Many setups already have the UIFork skill installed globally for agents.

If it is not available, add it from the upstream registry: