Add migration manifest tooling for downstream projects by f4-lex · Pull Request #984 · Frachtwerk/essencium-frontend

f4-lex · 2026-04-08T08:53:34Z

Summary

Add migration manifest format (packages/app/manifests/*.yaml) with initial manifests for v9.4.5 and v9.5.0
Add /author-migration skill that generates manifest drafts by diffing git tags
Companion plugin repo: Frachtwerk/essencium-frontend-migration-plugin

Closes #983

Test plan

Invoke /author-migration 9.5.0 and verify it produces a manifest matching packages/app/manifests/9.5.0.yaml
Validate both YAML manifests parse correctly
Install the migration plugin in a downstream project and test /migrate-essencium-frontend

Design for AI-powered migration tooling that helps downstream projects update their essencium-frontend based codebases. Covers change classification (7 categories), migration manifest format, authoring skill for this repo, and marketplace plugin for downstream.

Create a Claude Code skill that automates migration manifest authoring. When invoked, it diffs git tags, classifies changes into 7 categories (dependency_migration, infrastructure, translation, env_variable, new_file, file_removal, file_tracking), and generates a YAML manifest in packages/app/manifests/.

vercel · 2026-04-08T08:53:40Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview	Apr 14, 2026 7:40pm
docs	Ready	Preview	Apr 14, 2026 7:40pm
essencium-frontend-app	Ready	Preview, Comment	Apr 14, 2026 7:40pm

PhilKsr · 2026-04-14T11:52:47Z

Missing manifests for existing release tags
The following release tags have no corresponding manifest:

Tag	Gap
7.7.1	between 7.7.0 and 7.8.0
7.9.2	between 7.9.1 and 7.10.0
9.4.1	between 9.4.0 and 9.4.4
9.4.2	between 9.4.0 and 9.4.4
9.4.3	between 9.4.0 and 9.4.4
9.4.6	after 9.4.5

Plugin impact:
The plugin lists manifests via GitHub API and builds the migration path from them. A downstream project on e.g. 9.4.2 won't find a matching manifest and either can't start the migration, or skips straight to 9.4.4 — unclear whether changes from 9.4.0->9.4.4 are then fully covered.

Options:

Add empty manifests (changes: []) so the chain is gapless
Or explicitly document in the plugin that only certain versions have manifests, and adjust the matching logic

PhilKsr · 2026-04-14T11:54:59Z

pr field is inconsistently present
Some manifests have a pr link on every entry (e.g. 6.0.0.yaml)
Others omit it on most entries (e.g. 7.4.0.yaml)
Suggestion: Clarify in author skill: "pr is recommended wherever a PR exists; omit only for multi-PR changes or direct pushes"

PhilKsr

Well-designed system. The split between "manifest authoring" (upstream) and "manifest consuming" (downstream) is clean. The 7 change types cover the relevant migration scenarios, the version chain from 6.0.0 to 9.5.0 is nearly complete, and the plugin workflow (DETECT -> EXECUTE -> COMPLETE) is logically structured.

There are a few places where the two repos are inconsistent, and some data issues in the manifests.

- Fix 8.1.0 manifest from field (was 7.10.0, should be 8.0.0) - Add default field to env_variable schema in author skill - Clarify pr field guidance (include wherever a PR exists) - Document release tag convention in CLAUDE.md

f4-lex · 2026-04-14T19:41:00Z

Going with option 2 — not all versions will have manifests, and that is by design. Patch releases that only touch library internals or docs do not need one.

Updated the plugin (Frachtwerk/essencium-frontend-migration-plugin@25d64c1) to:

Explicitly document that not all versions have manifests
Improve the migration path logic: when the user's current version has no manifest, the plugin finds the next available manifest and starts from there
Show a clear message in the migration path output (e.g., "Your version 9.4.2 has no manifest — starting from the next available: 9.4.4")

Plugin bumped to 0.2.0.

f4-lex · 2026-04-14T19:41:02Z

Updated the author skill guidance: pr links should be included wherever a PR exists. Omit only for changes that span multiple PRs or were direct pushes without a PR.

The existing manifests have inconsistent coverage because many were batch-generated from git history where PR attribution was not always extractable. Going forward, the skill will prompt the author to include them.

f4-lex added 7 commits April 8, 2026 09:47

docs: clarify how SCAN step identifies essencium-origin files

bff7911

docs: add migration automation implementation plan

1f2f45f

chore: add migration manifest for v9.4.5 (accessibility and CVE fixes)

51f291a

chore: add migration manifest for v9.5.0 (React Compiler + Next.js 16)

7b1eb31

chore: remove spec and plan docs from repository

10e25ce

vercel Bot deployed to Preview – docs April 8, 2026 08:53 View deployment

vercel Bot deployed to Preview – essencium-frontend-app April 8, 2026 08:54 View deployment

vercel Bot deployed to Preview – app April 8, 2026 08:55 View deployment

refactor: move author-migration skill to .claude/skills/

6ed441b

vercel Bot deployed to Preview – docs April 8, 2026 08:58 View deployment

vercel Bot deployed to Preview – essencium-frontend-app April 8, 2026 08:58 View deployment

vercel Bot deployed to Preview – app April 8, 2026 08:59 View deployment

docs: add CLAUDE.md with project purpose and structure

1e06e26

vercel Bot deployed to Preview – docs April 8, 2026 09:01 View deployment

docs: remove version numbers from CLAUDE.md tech stack

6c01275

vercel Bot deployed to Preview – essencium-frontend-app April 8, 2026 09:03 View deployment

vercel Bot deployed to Preview – app April 8, 2026 09:03 View deployment

vercel Bot deployed to Preview – docs April 8, 2026 09:04 View deployment

f4-lex added 4 commits April 8, 2026 11:06

chore: add migration manifests for v6.0.0, v6.1.0, v6.1.1

6cd962f

chore: add migration manifests for v7.0.0 through v7.3.0

d596459

chore: add migration manifests for v7.4.0 through v7.10.0

c552082

chore: add migration manifests for v8.1.0 through v9.4.4

846b568

vercel Bot deployed to Preview – app April 8, 2026 09:11 View deployment

vercel Bot deployed to Preview – essencium-frontend-app April 8, 2026 09:11 View deployment

vercel Bot deployed to Preview – docs April 8, 2026 09:11 View deployment

f4-lex added 2 commits April 8, 2026 11:49

fix: correct manifest schema violations in v6.0.0 through v7.3.0

53b61ef

fix: correct manifest schema violations in v7.4.0 through v9.4.0

b4b69bd

f4-lex added 2 commits April 8, 2026 11:54

fix: remaining schema violations in v7.4.0 and v7.8.0 manifests

1938fc0

chore: add migration manifest for v8.0.0

72b0df5

vercel Bot deployed to Preview – docs April 8, 2026 09:57 View deployment

vercel Bot deployed to Preview – essencium-frontend-app April 8, 2026 09:58 View deployment

vercel Bot deployed to Preview – app April 8, 2026 09:58 View deployment

PhilKsr assigned f4-lex Apr 14, 2026

PhilKsr self-requested a review April 14, 2026 11:46

PhilKsr requested changes Apr 14, 2026

View reviewed changes

Comment thread packages/app/manifests/8.1.0.yaml Outdated

Comment thread .claude/skills/author-migration/SKILL.md

Comment thread CLAUDE.md

fix: address code review feedback on migration tooling

165b89c

- Fix 8.1.0 manifest from field (was 7.10.0, should be 8.0.0) - Add default field to env_variable schema in author skill - Clarify pr field guidance (include wherever a PR exists) - Document release tag convention in CLAUDE.md

vercel Bot deployed to Preview – docs April 14, 2026 19:39 View deployment

vercel Bot deployed to Preview – essencium-frontend-app April 14, 2026 19:40 View deployment

vercel Bot deployed to Preview – app April 14, 2026 19:40 View deployment

f4-lex requested a review from PhilKsr April 14, 2026 19:42

PhilKsr approved these changes Apr 15, 2026

View reviewed changes

f4-lex merged commit 5948157 into main Apr 15, 2026
13 of 14 checks passed

f4-lex deleted the migration-automation branch April 15, 2026 07:40

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add migration manifest tooling for downstream projects#984

Add migration manifest tooling for downstream projects#984
f4-lex merged 19 commits into
mainfrom
migration-automation

f4-lex commented Apr 8, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Apr 8, 2026 •

edited

Loading

Uh oh!

PhilKsr commented Apr 14, 2026

Uh oh!

PhilKsr commented Apr 14, 2026

Uh oh!

PhilKsr left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

f4-lex commented Apr 14, 2026

Uh oh!

f4-lex commented Apr 14, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

f4-lex commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

vercel Bot commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

PhilKsr commented Apr 14, 2026

Uh oh!

PhilKsr commented Apr 14, 2026

Uh oh!

PhilKsr left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

f4-lex commented Apr 14, 2026

Uh oh!

f4-lex commented Apr 14, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

f4-lex commented Apr 8, 2026 •

edited

Loading

vercel Bot commented Apr 8, 2026 •

edited

Loading