remove-feature-flag

Remove stabilized feature flags from the Warp codebase with verification steps.

Updated Apr 28, 2026

Search Tags:#codebase #maintenance #refactor #remove #feature-flag #warp

Ready to run

npx skills add https://github.com/89jobrien/warpx --skill remove-feature-flag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remove-feature-flag
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/remove-feature-flag
Command: npx skills add https://github.com/89jobrien/warpx --skill remove-feature-flag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove a feature flag after it has been rolled out and stabilized in the Warp codebase.

Core Features & Use Cases

Structured removal workflow across the codebase to eliminate dead code and configuration.
Step-by-step guidance for updating Cargo features, enums, and conditional compilations.
Real-world scenario: decommissioning a permanent flag after production stability to reduce debt.

Quick Start

Identify the permanent feature flag and apply the documented steps in order.

Frequently Asked Questions about remove-feature-flag

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

FAQPage Schema

How do I safely remove a permanent feature flag from a Rust codebase?▼

To safely remove a permanent feature flag, you update Cargo features, enums, and conditional compilations across modules. This enforces consistency and eliminates dead code after production stabilization.

What is the best way to clean up obsolete feature flags after a rollout?▼

The best way to clean up obsolete feature flags is to follow a structured removal workflow that eliminates dead code and configuration. This step-by-step process guides you through updating cargo features and enums to reduce technical debt safely.

When should I decommission a feature flag in my codebase?▼

You should decommission a feature flag after it has been fully rolled out and stabilized in production. Removing it at this stage reduces technical debt while maintaining codebase stability.

Does removing a feature flag require updating conditional compilations and enums?▼

Yes, removing a feature flag requires updating conditional compilations and enums across all affected modules. This step-by-step guidance ensures that cargo features and runtime checks remain consistent throughout the codebase after removal.

What steps do I need to follow to update Cargo features when retiring a flag?▼

To update Cargo features when retiring a flag, you apply the documented removal steps in order across the codebase. This process guides you through updating enums, conditional compilations, and runtime checks before merging to ensure safe removal.

Why do I need verification steps before merging a feature flag removal?▼

You need verification steps before merging a feature flag removal to ensure the codebase remains consistent after eliminating dead code and configuration. This safe removal process enforces stability after production stabilization by validating all module updates.