feature-flag-lifecycle

Audit feature-flag hygiene across providers and codebases.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill feature-flag-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flag-lifecycle
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/feature-flag-lifecycle
Command: npx skills add https://github.com/FrogAi/Xenopus --skill feature-flag-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production-grade feature-flag lifecycle auditor. It analyzes every flag across the organization's feature-flag provider (LaunchDarkly / Unleash / Split / Flagsmith / OpenFeature-compatible / homegrown config), cross-reference against code, and detects stale flags (fully rolled out 100% for >30d, fully off for >30d, never evaluated in >60d, abandoned / orphaned / untouched-for-90d), misconfigured flags (default variation inverted, percentage rollouts stuck mid-rollout, kill-switch-shaped but not a kill switch), and cleanup candidates. Never flips or deletes flags. Never edits code. Read-only.

Core Features & Use Cases

  • Live-practices fetch for up-to-date guidance from industry sources and provider docs.
  • Live provider inventory across LaunchDarkly, Unleash, Split, Flagsmith, and OpenFeature-compatible configs with per-flag metadata.
  • Code-reference mapping to locate where flags are used and how they influence behavior.
  • Chain-of-verification and risk scoring to prioritize safe cleanup and governance.
  • CoVe-assisted cleanup scaffolding and optional PR draft generation for safe changes.

Quick Start

Audit the feature-flag hygiene across providers and code without altering any flags.

Frequently Asked Questions about feature-flag-lifecycle

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

FAQPage Schema
How do I audit feature flags for stale or misconfigured configurations?

To audit feature flags, you analyze provider inventory and codebase references to detect stale flags, misconfigured variations, and stuck percentage rollouts. This process surfaces a ranked cleanup plan without altering any existing flags.

What is a stale feature flag and how is it identified?

A stale feature flag is fully rolled out for over 30 days, fully off for over 30 days, never evaluated for over 60 days, or untouched for 90 days. Identification requires cross-referencing provider metadata against code evaluations.

Does feature flag cleanup work with LaunchDarkly and Unleash?

Feature flag cleanup works with LaunchDarkly, Unleash, Split, Flagsmith, and OpenFeature-compatible configurations. It fetches live provider inventory and maps code references across these platforms to identify cleanup candidates.

How do I map feature flag code references safely?

You map feature flag code references by cross-referencing provider inventory against your codebase to locate where flags influence behavior. This read-only analysis ensures no flags are flipped, deleted, or edited during mapping.

What is the best way to generate cleanup plans for abandoned feature flags?

The best way to generate cleanup plans for abandoned flags is applying chain-of-verification and risk scoring to prioritize safe removal. This provides optional cleanup scaffolds and PR drafts without directly editing code.