Skip to content
Skills Library
Programming · Review & audit

migrate

/migrate

Identify breaking changes between custom element manifest versions and suggest migration steps. Use when the user asks to "migrate", "upgrade components", "find breaking changes", "compare manifests", "what changed between versions", or mentions "deprecation" or "migration guide".

Repository
cem ↗
Licence
GPL-3.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Identify breaking changes between custom element manifest versions and suggest migration steps. Use when the user asks to "migrate", "upgrade components", "find breaking changes", "compare manifests", "what changed between versions", or mentions "deprecation" or "migration guide".

Triggers from the description

migrateupgrade componentsfind breaking changescompare manifestswhat changed between versionsdeprecationmigration guide
Original author description

Identify breaking changes between custom element manifest versions and suggest migration steps. Use when the user asks to "migrate", "upgrade components", "find breaking changes", "compare manifests", "what changed between versions", or mentions "deprecation" or "migration guide".

How it works

  1. Workflow
  2. Guidelines
Original SKILL.md headings · 128 lines, 579 words
SKILL.md preview
---
name: migrate
description: >
  Identify breaking changes between custom element manifest versions and suggest
  migration steps. Use when the user asks to "migrate", "upgrade components",
  "find breaking changes", "compare manifests", "what changed between versions",
  or mentions "deprecation" or "migration guide".
tools: Read, Glob, Grep, Bash
---

# Migration Assistant

Compare custom element manifests across versions to identify breaking changes and generate migration guidance.

## Workflow

### Phase 1: Identify Versions to Compare

Determine the two versions to compare. Sources:

1. **Git-based**: Compare the current manifest against a previous git ref
   ```bash
   git show {ref}:path/to/custom-elements.json
   ```

2. **File-based**: User provides two manifest files or paths

3. **Package-based**: Compare installed version against a target version
   - Read current manifest from `node_modules/{package}/custom-elements.json`
   - Check the target version's manifest

Read the current project's elements for context:

```text
cem://elements
```

### Phase 2: Diff Analysis

Compare the two manifests and categorize changes:

#### Removed (Breaking)
- **Removed elements**: Tag names that no longer exist
- **Removed attributes**: Attributes dropped from an element
- **Removed slots**: Named slots that no longer exist
- **Removed events**: Events that are no longer fired
- **Removed CSS parts**: Parts no longer exposed
- **Removed CSS custom properties**: Theming properties removed

#### Changed (Potentially Breaking)
- **Renamed attributes**: Attribute name changed (detect via similar names + same type)
- **Type changes**: Attribute type changed (e.g., `string` to `enum`, `boolean` to `string`)
- **Enum value changes**: Valid values added or removed
- **Default value changes**: Different default behavior
- **Slot renamed**: Named slot changed (detect via similar names)
- **Event detail changes**: Event detail type modified
- **CSS property renamed**: Custom property name changed

#### Added (Non-Breaking)
- **New elements**: Newly available tag names
- **New attributes**: Additional configuration options
- **New slots**: Additional content areas
- **New events**: Additional observable state changes
- **New CSS parts/properties/states**: Additional styling hooks

#### Deprecated
- **Deprecated attributes**: Marked for future removal
- **Deprecated elements**: Elements scheduled for removal
- Look for `deprecated` field or deprecation notes in descriptions

### Phase 3: Impact Assessment

For each breaking change, search the project for affected usage:

- Search HTML files for removed/changed element tag names
- Search for removed attribute names on affected elements
- Search for removed event listeners
- Search CSS for removed parts and custom properties

Report the number of affected files and locations.

### Phase 4: Migration Report

````markdown
## Migration Report: {package} {old-version} -> {new-version}

### Summary
- Breaking changes: X
- Potentially breaking: X
- New features: X
- Deprecations: X
- Files affected: X

### Breaking Changes

#### 1. `<old-element>` removed
**Impact**: Used in X files
**Migration**: Replace with `<new-element>`
```diff
- <old-element attr="value">content</old-element>
+ <new-element attr="value">content</new-element>
```
**Files affected**:
- `src/pages/login.html:15`
- `src/components/form.html:42`

#### 2. `variant` attribute on `<prefix-button>` renamed to `appearance`
**Impact**: Used in X files
**Migration**: Rename the attribute
```diff
- <prefix-button variant="primary">
+ <prefix-button appearance="primary">
```

### Deprecation Warnings

[Items that still work but will break in a future version]

### New Features

[Brief summary of what's new — the user might want to adopt these]

### Recommended Migration Order

1. [Fix breaking changes that cause build/runtime errors first]
2. [Address deprecation warnings]
3. [Optionally adopt new features]
````

## Guidelines

- **Be conservative with "renamed" detection**: Only suggest a rename if the types match and names are similar — don't guess
- **Show concrete diffs**: Every breaking change should include a before/after code example
- **Find all affected files**: Don't just describe the change abstractly — show where it matters in the project
- **Distinguish runtime breaks from cosmetic changes**: A removed attribute is worse than a changed default
- **Suggest incremental migration**: If there are many changes, recommend an order that keeps the project functional at each step

Versions

RepositoryScoreLicence
This page · bennypowers/cem100GPL-3.0
marcel-bich/marcel-bich-claude-marketplace100MIT
abatyuk/okf100MIT
markusleben/ha-nova100MIT
toss/es-toolkit100MIT
rvdbreemen/adr-kit100MIT
asgeirtj/system_prompts_leaks100CC0-1.0
madappgang/magus100MIT
hainrixz/claude-db100MIT

Database snapshot: 13.11.2026 · package version c8bbfa0af6d2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100skill-migrate
    AL version migration for Business Central. Use when upgrading extensions between BC versions, handling breaking changes, or implementing rollback strategies.
  • 100skill-migrate
    AL version migration for Business Central. Use when upgrading extensions between BC versions, handling breaking changes, or implementing rollback strategies.
  • 100migrate-ai-sdk-v6-to-v7
    Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep.
  • 98maintainx-upgrade-migration
    Migrate MaintainX API versions and handle breaking changes. Use when upgrading API versions, handling deprecations, or migrating between MaintainX API releases. Trigger with phrases like "maintainx upgrade", "maintainx api version", "maintainx migration", "maintainx breaking…
  • 100linear-upgrade-migration
    Upgrade Linear SDK versions and migrate breaking changes. Use when updating to a new SDK version, handling deprecations, or migrating between major Linear API versions. Trigger with phrases like "upgrade linear SDK", "linear SDK migration", "update linear", "linear breaking…
  • 100evernote-upgrade-migration
    Upgrade Evernote SDK versions and migrate between API versions. Use when upgrading SDK, handling breaking changes, or migrating to newer API patterns. Trigger with phrases like "upgrade evernote sdk", "evernote migration", "update evernote", "evernote breaking changes".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.