Orchestrate multi-stage API, column, and capability removal across repositories.
npx skills add https://github.com/highflame-ai/ai-factory --skill deprecate-highflame-ai
Please help me install this Agent Skill. Skill: deprecate Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/deprecate Command: npx skills add https://github.com/highflame-ai/ai-factory --skill deprecate-highflame-ai
This skill solves the high-risk challenge of removing APIs, database columns, or capabilities without breaking downstream consumers or causing production outages.
Use the deprecate skill to initiate the safe removal process for the legacy user-auth-v1 endpoint across all configured repositories.
High-intent search queries and answers about installing and using this skill.
To safely remove legacy APIs and database columns across multiple repositories, you need a multi-stage deprecation lifecycle that includes cross-repo impact analysis, consumer migration, and verified code deletion to prevent breaking downstream consumers.
The best way to deprecate an API endpoint without causing outages is to follow a staged removal workflow: apply deprecation markers, verify all internal and external consumers have migrated, and execute final code deletion only after observability-driven verification.
Cross-repo impact analysis works by automatically identifying all callers of a symbol across multiple repositories, ensuring that engineering workflows can assess downstream dependencies and apply non-breaking changes before actual code cleanup occurs.
Yes, you can use a staged removal workflow for database columns and capabilities. The deprecation process orchestrates non-breaking changes by guiding you through marking elements as deprecated, migrating consumers, and verifying removal against spec-registry standards.
You need a deprecation lifecycle for code cleanup when retiring legacy APIs, database columns, or capabilities requires adherence to organizational spec-registry standards and observability-driven verification to ensure non-breaking changes across consumers.
Automated code deletion during API migration is constrained by the need for verified consumer migration and observability-driven checks; final removal cannot proceed safely until all internal and external callers are confirmed to be migrated.
bordenetIdentify all consumers of a code symbol before modifying it.
AissenLiuCoordinate subagents to execute plan-driven development tasks with two-stage reviews.
nikblanchetIdentify deprecation warnings and migrate code to recommended APIs.
mgreenlyEnforce project rules for directory, tool, and git command constraints.
