Individual skill
generic-migration
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.
skills/generic-migration/SKILL.md
Source commit 3331b903f0e954d59ac69be1a75fd4fd7e1de20e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,784
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentteams Repository topic
- dsh Repository topic
- deepseekharness Repository topic
- dsh-agent-teams Repository topic
- dsh-plugin Repository topic
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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