Deprecation and migration
SkillAI & modelsPlan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Deprecation and migration skill
What this skill tells your AI
The instructions your AI receives, as published by charlieviettq/awesome-agent-skill in .claude/skills/deprecation-and-migration/SKILL.md and read by ahel’s review.
Decision questions
- Does the old system still provide unique value?
- How many consumers? Migration cost each?
- Is replacement production-proven?
- Cost of NOT deprecating (security, maintenance)?
Compulsory vs advisory
| Type | When |
|---|---|
| Advisory | Stable legacy, optional migration |
| Compulsory | Security risk, blocks progress — need tooling + deadline |
Default advisory unless risk justifies force.
Process
- Build replacement first
- Announce — status, replacement, migration guide, timeline
- Migrate consumers incrementally; owner migrates users when possible
- Remove only after zero active usage verified
Patterns
| Pattern | Use when |
|---|---|
| Strangler | Gradual traffic shift |
| Adapter | Old interface, new implementation |
| Feature flag | Per-consumer or cohort cutover |
Zombie code signals
- No maintainer, active dependents, failing tests ignored, stale deps
Output
Deprecation notice + migration steps + removal checklist.
Signals
- GitHub stars
- 26
- Forks
- 9
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
deprecation-and-migration-charlieviettq- Source
- github.com/charlieviettq/awesome-agent-skill