deprecation-and-migration SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.

deprecation-and-migration from naimkatiman/continuous-improvement is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add naimkatiman/continuous-improvement/deprecation-and-migration@git:20260507.4a6727c

Pins git:20260507.4a6727c in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

naimkatiman/continuous-improvement

Path

third-party/addy-agent-skills/skills/deprecation-and-migration/SKILL.md

Versions recorded

1

Latest version

git:20260507.4a6727c, committed May 7, 2026

Size

9,000 bytes

Repository stars

9

License

MIT

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Deprecation and Migration

## Overview

Code is a liability, not an asset. Every line of code has ongoing maintenance cost — bugs to fix, dependencies to update, security patches to apply, and new engineers to onboard. Deprecation is the discipline of removing code that no longer earns its keep, and migration is the process of moving users safely from the old to the new.

Most engineering organizations are good at building things. Few are good at removing them. This skill addresses that gap.

## When to Use

- Replacing an old system, API, or library with a new one
- Sunsetting a feature that's no longer needed
- Consolidating duplicate implementations
- Removing dead code that nobody owns but everybody depends on
- Planning the lifecycle of a new system (deprecation planning starts at design time)
- Deciding whether to maintain a legacy system or invest in migration

## Core Principles

### Code Is a Liability
…

Read the whole file at its exact version.

How to install

mdr add naimkatiman/continuous-improvement/deprecation-and-migration@sha256:bf2d9b4e3bc635b3

[![mdr](https://markdownregistry.com/badge/art_jwzd7opvtc2mo5el.svg)](https://markdownregistry.com/a/art_jwzd7opvtc2mo5el)

Versions

The registry has recorded 1 version of this file, committed on May 7, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_jwzd7opvtc2mo5el
GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/deprecation-and-migration
GET https://markdownregistry.com/api/v1/blob/bf2d9b4e3bc635b32e8de70b0ab41e4395d7b585e6474347c53ce89d45fbdb75

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from naimkatiman/continuous-improvement

Every file in naimkatiman/continuous-improvement

Other files named deprecation-and-migration

Browse by kind, by grade A, or by owner.