charlieviettq/awesome-agent-skill / .claude/skills/deprecation-and-migration
deprecation-and-migration
VerifiedPlan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
SKILL.md
View on GitHub---
name: deprecation-and-migration
description: "Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules."
allowed-tools: Read, Glob, Grep
---
# Deprecation and migration
## Decision questions
1. Does the old system still provide unique value?
2. How many consumers? Migration cost each?
3. Is replacement production-proven?
4. 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
1. **Build replacement** first
2. **Announce** — status, replacement, migration guide, timeline
3. **Migrate consumers** incrementally; owner migrates users when possible
4. **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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |