Verified:GitHub

feature-flag-clean-up

Remove rolled-out feature flags from a repository codebase while preserving enabled behavior via search and inline strategies.

1|Updated Jan 17, 2026

Search Tags:#refactoring #cleanup #codebase maintenance #feature flag #software integrity

Ready to run

npx skills add https://github.com/alexandersumer/config --skill feature-flag-clean-up

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-flag-clean-up
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/feature-flag-clean-up
Command: npx skills add https://github.com/alexandersumer/config --skill feature-flag-clean-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for cleaning up rolled-out feature flags while ensuring that the enabled behavior is preserved, simplifying the process and maintaining system integrity.

Core Features & Use Cases

Flag Cleanup: Removes fully rolled-out feature flags, leaving the enabled behavior intact.
Behavior Preservation: Ensures that the core functionality remains active post-cleanup.
Comprehensive Removal: Eliminates checks, aliases, constants, config, tests, and docs related to the flag.
Search and Inline: Searches for flag references and inlines enabled branches, deletes disabled tests, and removes unused imports.
Reusability and Testing: Promotes the reuse of proof for validity and runs targeted real path checks.

Quick Start

Use the feature-flag-clean-up skill to remove the 'flag_key' from the codebase, ensuring the preserved behavior remains functional.

Frequently Asked Questions about feature-flag-clean-up

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

FAQPage Schema

How do I remove fully rolled-out feature flags from a codebase without breaking existing functionality?▼

Feature flag cleanup eliminates rolled-out flags from your codebase while preserving the enabled behavior by inlining active code branches, deleting disabled tests, and removing unused imports, constants, and config.

What does feature flag cleanup involve besides deleting the flag check?▼

Feature flag cleanup involves comprehensive removal of checks, aliases, constants, config, tests, and documentation related to the flag, while inlining the enabled branches and deleting disabled tests to maintain software integrity.

When should I clean up feature flags in my codebase?▼

You should clean up feature flags when they are fully rolled-out and no longer needed, allowing the cleanup process to preserve the enabled behavior while eliminating all related code elements and maintaining system integrity.

Can this feature flag cleanup process preserve the enabled behavior of my code?▼

Yes, feature flag cleanup preserves the enabled behavior by inlining active code branches and removing only disabled paths, tests, and unused imports related to the rolled-out flag.

How do I ensure software integrity when removing feature flags?▼

To ensure software integrity during feature flag removal, the process promotes reusing proof for validity and runs targeted real path checks to verify that the core functionality remains active post-cleanup.

Does feature flag cleanup remove related tests and documentation?▼

Yes, feature flag cleanup comprehensively eliminates disabled tests and documentation related to the flag, while inlining the enabled branches to ensure the core functionality remains active post-cleanup.