apoptosis-and-cell-death

Evaluate software components for deprecation, sunset, or deletion with structured lifecycle analysis.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill apoptosis-and-cell-death
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apoptosis-and-cell-death
Source: https://github.com/NlightNFotis/skills/tree/main/apoptosis-and-cell-death
Command: npx skills add https://github.com/NlightNFotis/skills --skill apoptosis-and-cell-death

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide when old services, APIs, flags, and code should be deliberately removed instead of indefinitely preserved. It turns vague deprecation thinking into a structured lifecycle review that separates healthy sunsetting from risky, incident-driven rip-outs.

Core Features & Use Cases

  • Deprecation diagnosis: Distinguishes planned, orderly removal from emergency removal with collateral damage.
  • Lifecycle design: Defines death signals, survival signals, and step-by-step sunset cascades for components that should end.
  • Cleanup planning: Identifies zombie services, senescent features, dead code, lingering dashboards, and other leftovers that keep operational and cognitive costs alive.
  • Use cases: Useful for API sunsets, feature-flag cleanup, migration completion reviews, dead-code audits, and post-incident analysis where retention created risk.

Quick Start

Ask the apoptosis-and-cell-death skill to evaluate a legacy API or service, identify its death trigger, classify its pathology, and produce a full deprecation cascade.

Frequently Asked Questions about apoptosis-and-cell-death

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to plan an API deprecation and service retirement process?▼

Dead code cleanup classifies components by pathology, identifying survival signals and death triggers to separate healthy sunsetting from risky necrotic removal that causes operational incidents and collateral damage.

How do I audit my codebase for dead code and senescent features?▼

A dead code audit identifies senescent features, lingering dashboards, and zombie services by evaluating retention pathology, tagging autophagy opportunities, and producing a complete deletion cascade for technical debt removal.

Can I use a structured lifecycle analysis for feature flag cleanup and migration completion?▼

Lifecycle analysis applies to feature flag cleanup and migration completion reviews by identifying death receptors and survival signals, ensuring only fully migrated components are sunset while active dependencies are preserved.

When should I avoid deleting aging systems and legacy code?▼

Avoid deleting aging systems when survival signals indicate active dependencies, as emergency removal without classifying apoptosis versus necrosis risks operational incidents caused by pathological retention and collateral damage.

Why does preserving deprecated services indefinitely increase operational risk?▼

Preserving deprecated services indefinitely increases operational risk by sustaining cognitive and operational costs of zombie services, leading to incidents where pathological retention forces emergency rip-outs instead of planned apoptosis.