LowPR-scope

Clean up feature flags when retiring code (avoid zombie flags)

When removing or decommissioning a feature, ensure the associated feature flag is also removed from: - application code paths, - config/registry files (e.g., flags.ts, config.json), and - analytics/feature flag tools (if applicable). If a PostHog (or similar) MCP is available, verify the flag is disabled/removed and not referenced elsewhere. Otherwise, require a repo-wide search evidence in the PR.

Add to Mesrai Open workspace

Why this matters

Prevents accumulating dead flags, reduces complexity, and avoids accidental re-enablement of retired code paths.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

Deletes old code but leaves `flag.checkoutV2` referenced in config and analytics.

Prefer

Removes flag from code + config + cleans up tracking; documents rollout completion.

More snippets

Bad

Removed feature code; flag key still exists in flags.ts

Good

Flag removed everywhere (code/config/analytics)

Related rules

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes