Skip to content
SkillModel-led2,740 tokens in use

deprecation-and-migration

Plan the removal of old systems with deprecation decisions, migration patterns and expand/contract schema changes.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/deprecation-and-migration
npx skills add addyosmani/agent-skills --skill deprecation-and-migration
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing deprecation-and-migration costs

68tokens idle
2,740tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Deprecation and Migration treats code as a liability and guides an agent through removing what no longer earns its keep. It covers the decision to deprecate, advisory and compulsory deprecation, and a four-step migration process from building the replacement to deleting the old system.

The skill includes the strangler, adapter and feature flag patterns, a worked expand, backfill and contract example for renaming a database column without downtime, and guidance on zombie code.

What You Get

  • A deprecation decision checklist
  • A migration process with a notice template and the Churn Rule
  • Strangler, adapter, feature flag and expand/contract patterns
  • Red flags and verification lists for deprecations and schema migrations

Common Use Cases

  • Replacing an old API or library
  • Renaming or dropping a database column in production
  • Sunsetting an unused feature
  • Deciding what to do with unowned legacy code

What Makes It Unique

Database schema migration gets its own worked procedure: expand, dual-write, backfill in batches, switch reads and drop in a later deploy, with a tested down path at each step. The skill also states the Churn Rule, which makes the owner of deprecated infrastructure responsible for migrating its users.

Under The Hood

The skill is a single SKILL.md of instructions with TypeScript and SQL-oriented examples. It runs no scripts and reaches no services. It cites Hyrum’s Law and links to the incremental-implementation skill for slicing each phase.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers