KeyanVakil/feature-flag-cleanup

Feature flags are temporary. Someone has to clean them up. Today it's you.

Steps

1. Find every feature flag in the codebase. Search for:

   • featureFlags., flags., isEnabled(, getFlag(, FEATURE_, FF_
   • LaunchDarkly: ldClient.variation(, useFlags(, useLDClient(
   • Statsig: useGate(, checkGate(, statsig.checkGate(
   • Homegrown: look for a flags config object/file

2. For each flag found, classify it:

Classification	Signal
Always-on	Default is true and no code path sets it false
Always-off	Default is false, feature never shipped, code path is dead
Actively used	Referenced in flag service/dashboard with active experiments
Abandoned	Referenced in code but doesn't exist in the flag service
Graduated	Shipped to 100% of users, no longer needs a flag

3. For each always-on or graduated flag:

   • Remove the flag check
   • Keep the feature-enabled code path
   • Delete the feature-disabled code path
   • Clean up any now-unreachable imports

4. For each always-off or abandoned flag:

   • Remove the flag check
   • Delete the feature-enabled code path entirely
   • Keep the feature-disabled code path (it's the live behavior)

5. For each actively used flag: leave it alone, document it.

6. After cleanup, run a search to confirm no remaining references to removed flag names.

Output

FLAGS FOUND: X total

REMOVED (always-on / graduated):
- FLAG_NEW_CHECKOUT — removed, kept new checkout flow
- FLAG_DARK_MODE — removed, dark mode now default

REMOVED (always-off / abandoned):
- FLAG_EXPERIMENTAL_SEARCH — removed, deleted dead code (~200 lines)

LEFT ALONE (active):
- FLAG_PRICING_TEST — active A/B test, leave it

NET CODE DELETED: ~X lines

Rules

• When in doubt, don't delete — flag it as "possibly stale" and ask
• Delete code, not just the flag check — dead code is worse than a flag
• If a flag guards a payment or auth flow, get a second pair of eyes before deleting
• Run tests after each flag removal, not at the end