Skill Details
Runtime
(claude-5-5-sonnet)
Example user message
[userMessage]: Here's our flag inventory: enable-new-checkout-flow, state: enabled, rollout: 100%, environments: prod/staging/dev, last modified: 14 months ago, referenced in CheckoutController.java and checkout-config.yaml. Is it safe to delete?
Example agent response
Risk Level: Low (Safe to remove).
enable-new-checkout-flow is at 100% rollout in prod, staging, and dev, and has been untouched for 14 months - the flag check is now always true, so the "old" branch is dead code.
Stale Flags: enable-new-checkout-flow (100% everywhere, 14 months stale).
Cleanup Candidates: enable-new-checkout-flow - high confidence.
Safer Removal Plan:
1. Confirm the flag reads 100% in every environment (prod/staging/dev) right now, not just in this snapshot.
2. Search the codebase for every reference - found in CheckoutController.java and checkout-config.yaml.
3. Remove the flag check in CheckoutController.java, keeping only the "new" branch; delete the now-unreachable old branch.
4. Remove the flag entry from checkout-config.yaml and the flag-management dashboard.
5. Deploy and monitor checkout conversion for 48-72 hours before considering the cleanup final.
Warnings: none - no environment drift and no partial rollout detected.
Get this skill + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View Select
Instant access
Commercial use
Money‑backBy purchasing this skill, you agree to our terms of service
19
Views
CLAUDE-5-5-SONNET
Paste your feature flag inventory (names, states, rollout percentages, environments, last-modified dates, and the code referencing them) and get an instant cleanup audit: which flags are safe to delete, which are stale technical debt, and which carry hidden deployment risk if removed carelessly. Outputs a clear Risk Level, Stale Flag list, Cleanup Candidates, and a step-by-step Safer Removal Plan so you never kill a flag still gating something critical.
...more
Added 1 week ago
