Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in…
Install Generic Migration
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/generic-migration .claude/skills/generic-migration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .claude/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/generic-migration .agents/skills/generic-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .agents/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/generic-migration .cursor/skills/generic-migration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .cursor/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git --path skills/generic-migration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/generic-migration .gemini/skills/generic-migration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .gemini/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/generic-migration .github/skills/generic-migration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .github/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oh-my-dsh/dsh-plugin-upgrade-skill generic-migration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/generic-migration .opencode/skills/generic-migration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "generic-migration" agent skill from https://github.com/oh-my-dsh/dsh-plugin-upgrade-skill/tree/main/skills/generic-migration into .opencode/skills/generic-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generic-migration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
generic-migration- GitHub stars
- 259
- Token cost
- ~1.3k tokens
- SKILL.md length
- 696 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in…
- Works in 6 steps: Ground rules → Inventory the coupling surface → Read the corridor, not just the endpoints → …
- Upgrading any plugin from one host-framework version to another without access to framework-specific migration notes
- SKILL.md covers 0. Ground rules, 1. Inventory the coupling…, 2. Read the corridor, not just… and 3. Map, then edit, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Generic Migration is an agent skill from oh-my-dsh/dsh-plugin-upgrade-skill. Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in layers. Use when upgrading any plugin from one host-framework version to another without access to framework-specific migration notes. Not a substitute for vendor release notes; contains no framework-specific facts.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. The repository describes itself as: 帮助插件自动随着dsh版本升级的skill. The licence is MIT.
When your agent uses it
- Upgrading any plugin from one host-framework version to another without access to framework-specific migration notes
- Tasks that involve Changelog and release notes
Example prompts
- “/generic-migration”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ef07576. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Generic Migration loads about 1.3k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 696 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from oh-my-dsh/dsh-plugin-upgrade-skill at commit ef07576, republished under its MIT licence (© oh-my-dsh). 696 words, ~1,314 tokens.
Download SKILL.mdSave it as
.claude/skills/generic-migration/SKILL.md (or your agent's skills folder).- name
- generic-migration
- description
- Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in layers. Use when upgrading any plugin from one host-framework version to another without access to framework-specific migration notes. Not a substitute for vendor release notes; contains no framework-specific facts.
- license
- MIT
Generic Plugin Migration Methodology
A disciplined procedure for moving a plugin across an upstream release that may contain breaking changes. Everything here is framework-agnostic: no product names, no version numbers, no API identifiers. Pair it with the upstream project's own changelog and release notes whenever those exist.
0. Ground rules
- Never migrate blind. If you have not read the upstream changelog for every version in the corridor (start → target, inclusive), you are guessing.
- Inventory before edits. A written list of what the plugin touches beats discovering breakage one crash at a time.
- Change one layer at a time, and keep the old install runnable until the new one is proven (side-by-side installs, separate data directories).
1. Inventory the coupling surface
Before touching code, scan the plugin read-only and record every place it couples to the host. A generic coupling checklist:
- Manifest / metadata — declared compatibility ranges, entry points, permissions, capabilities the plugin requests.
- Host API imports — every module, symbol, or type imported from the host or its SDK; note which are used at load time vs call time.
- Lifecycle & events — activation hooks, event subscriptions, disposal.
- Services & RPC — services the plugin consumes or exposes; inter-process or request/response channels and their payload shapes.
- UI contributions — commands, views, panels, menus, themes, keybindings.
- Persistence — files, databases, or key-value stores the plugin reads or writes, including schema versions and migration code.
- Process & I/O seams — spawned subprocesses, sockets, pipes, parsers of host-generated output (logs, CLI text, serialized state).
- Configuration — settings keys read/written, defaults the plugin relies on, user-facing documentation of those keys.
- Dependencies — packages shared with the host (risk of duplicate instances), peer ranges, runtime version floors.
For each item record: file/line, what exactly is coupled, and how confident you are. "No hit" is only meaningful after you state what you scanned and what you could not rule out.
2. Read the corridor, not just the endpoints
Changes across a release corridor interact. Read every intermediate release's notes and diff, and build a net-state table:
- A field removed in an intermediate version but restored later has zero net change — do not "migrate" it away.
- A rename that happened in two steps (A → B → C) is migrated straight A → C.
- Behavior changes (defaults, ordering, timing) are as breaking as API removals; list them explicitly.
Classify each upstream change as: breaking (must edit), behavioral (must re-verify), additive (optional), or informational.
Show full SKILL.md (296 more words)Show less
3. Map, then edit
Map every inventory hit (§1) to a corridor change (§2). Only then edit, in dependency order:
- Manifest and compatibility ranges first — the host may refuse to load anything else you fix.
- Host API surface: renames, removals, signature changes.
- Lifecycle/events/services.
- Persistence migrations (never mutate the user's only copy; write-migrate on first run with a backup, or fail closed).
- UI and configuration.
- Dependency alignment: shared packages must resolve to the host's instance; check for duplicate copies in the installed tree.
4. Verify in layers
Cheap layers first; each layer must pass before the next means anything:
- Static: typecheck, lint, the plugin's own unit tests.
- Install-time: the host accepts the manifest and loads the plugin without warnings.
- Cold start: a real host process boots with the plugin enabled; check logs for deprecation and fallback warnings, not just crashes.
- Functional probe: one real end-to-end path per major feature, including the features you did not migrate (silent behavior drift hides there).
- Data: migrate a copy of real persisted data; verify round-trip and downgrade behavior.
- Rollback rehearsal: prove you can go back — reinstall the old version against the migrated data and confirm it still works or that you have a restore path.
5. Discipline and pitfalls
- Prefer the host's documented replacement over re-implementing removed behavior yourself.
- Treat "it typechecks" as the beginning of verification, not the end.
- Deprecated-but-working is a scheduled failure: record it even if out of scope.
- If a change's semantics are unclear, read the upstream source at the target tag; do not guess shapes from a one-line changelog entry.
- Keep a written migration log: what you changed, why, and what you verified. It is the artifact that lets someone else trust the migration.
© oh-my-dsh, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/generic-migration of oh-my-dsh/dsh-plugin-upgrade-skill.
Open the folder on GitHubat commit ef07576
Compare with similar skills
Generic Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Generic Migration this skilloh-my-dsh/dsh-plugin-upgrade-skill | 259 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from oh-my-dsh/dsh-plugin-upgrade-skill
Plugin Fleet Sweep
oh-my-dsh/dsh-plugin-upgrade-skill
A skill your agent uses when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces…
Plugin Runtime Debug
oh-my-dsh/dsh-plugin-upgrade-skill
A skill your agent uses when an installed DSH Web plugin misbehaves only at runtime in the browser — paste/attachment/composer features that work once then fail, chips or panels showing stale…
Related
Categories
Questions about Generic Migration
What does Generic Migration do?
Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in…. Generic Migration is an agent skill from oh-my-dsh/dsh-plugin-upgrade-skill. Framework-agnostic methodology for migrating a plugin, extension, or integration across a breaking upstream release — inventory coupling points, classify changes, stage the migration, and verify in layers.
When should I use Generic Migration?
Generic Migration fits situations like: upgrading any plugin from one host-framework version to another without access to framework-specific migration notes; tasks that involve Changelog and release notes.
How do I install Generic Migration in Claude Code?
Run `npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a claude-code`. Or copy the skill folder (skills/generic-migration in oh-my-dsh/dsh-plugin-upgrade-skill) into .claude/skills/generic-migration in your project. Claude Code loads it when a task matches its description.
How do I install Generic Migration in Codex?
Run `npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a codex`. Or copy the skill folder (skills/generic-migration in oh-my-dsh/dsh-plugin-upgrade-skill) into .agents/skills/generic-migration in your project. Codex loads it when a task matches its description.
Can I use Generic Migration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oh-my-dsh/dsh-plugin-upgrade-skill --skill generic-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generic-migration, .gemini/skills/generic-migration, .github/skills/generic-migration and .opencode/skills/generic-migration in your project.
What does Generic Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Generic Migration is instructions for the agent only.
Does Generic Migration access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Generic Migration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Generic Migration use?
Generic Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Generic Migration use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Generic Migration?
Skills that share tags, products or a category with Generic Migration: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Generic Migration?
oh-my-dsh (a GitHub organization) maintains it in oh-my-dsh/dsh-plugin-upgrade-skill, which has 259 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: oh-my-dsh/dsh-plugin-upgrade-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.