deprecation-handler_skill

This skill identifies, assesses, and migrates deprecated APIs and patterns to safe, modern alternatives, reducing risk and speeding refactoring.

Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alienfast/claude --skill deprecation-handler

SKILL.md8.7 KB

Overview

This skill identifies, assesses, and migrates deprecated APIs, types, functions, and modules using safe, incremental patterns. It produces a prioritized migration plan, executes replacements with tests, and validates changes to prevent regressions. The goal is to modernize legacy code and remove deprecation risks with minimal disruption.

How this skill works

It scans compiler/linter output, dependency reports, and IDE warnings to catalog deprecations with location, message, and suggested replacements. It classifies each item by priority, estimates effort and risk, and generates a step-by-step migration plan. Execution follows an incremental pattern: add modern implementation alongside legacy code, validate equivalence with tests, replace usage, then remove the old API. Final validation runs type checks, linting, tests, and build verification to prevent regressions.

When to use it

When compiler or linter outputs deprecation warnings
While upgrading dependencies that introduce breaking changes
When modifying files that contain deprecated code (fix-on-touch)
During codebase modernization or framework migrations
When investigating build warnings or IDE strikethrough indicators

Best practices

Catalog every deprecation with file, line, message, replacement, and tracking issue
Classify by priority (Immediate, High, Medium, Low) and plan incremental work
Prefer official migration guides and stable replacements over ad hoc fixes
Add or verify test coverage before replacing deprecated behavior
Perform changes file-by-file, run tests after each change, and keep commits focused
Document unfixed deprecations with reason, migration guide link, sunset date, and tracking issue

Example use cases

Replace deprecated React lifecycle methods with hooks across a component library
Migrate from an unmaintained npm package to a modern alternative with minimal breaking changes
Update TypeScript types and APIs after a major dependency upgrade that deprecates old types
Resolve build-time deprecation warnings discovered during CI or local tsc runs
Track and schedule low-priority deprecations for future sprints while documenting blockers

FAQ

Classify by impact: fix immediately for security or breaking changes, prioritize simple direct replacements and high-usage items, and schedule medium/low priority work when it requires larger refactors or coordination.

What if a deprecated API has no direct replacement?

Document the absence of a replacement, implement a safe custom alternative if feasible, mark the file with migration notes, and track the issue until a supported path exists.