FlagFatigue finds zombie feature flags and opens safe cleanup PRs automatically. It scans flag usage inside your GitHub Actions runner, cross-references lifecycle data from LaunchDarkly or PostHog, and identifies dead rollout logic. High-confidence flags are safely rewritten, while ambiguous cases stay for human review. No auto-merges, no blind AI edits—your CI stays in control. Delete feature flag debt before it becomes permanent. 🚩
No reviews yetBe the first to leave a review for FlagFatigue
Maker
📌
Hey Product Hunt 👋 I'm Ayush, the maker of FlagFatigue 🪦
The idea came from a simple observation: developers are great at adding feature flags and terrible at deleting them.
A feature ships. The flag reaches 100%. Everyone moves to the next sprint.
Six months later, someone finds the conditional and asks:
“Can we delete this?”
Nobody wants to be the person who says yes 😅
I built FlagFatigue to automate the boring investigation around that question.
It scans flag references in your own GitHub Actions runner, checks their lifecycle state against LaunchDarkly or PostHog, and opens a cleanup PR with the evidence and context needed to review it.
One thing I cared about from day one was safety.
FlagFatigue never auto-merges. A flag at 100% rollout alone is not enough to blindly delete it. Ambiguous cases are surfaced for humans, and your existing CI remains the final gate.
The first version supports JS, TS, JSX, TSX and Python.
I'd genuinely love feedback from engineers dealing with feature flags:
What's the oldest flag still sitting in your codebase? 🚩🪦
Report
honestly this looks super useful, but one thing that would make me trust it even more is a dry run mode that shows the exact diff before anything gets pushed. like basically a sandbox preview so you can sanity check the rewrites against your real codebase without committing to a PR yet.
Report
One thing I'd love to see is a dashboard view showing the "cleanup velocity" over time, like how many flags were flagged, reviewed, and merged per week. Right now the value feels invisible once the PRs land. Surfacing trends would really help convince skeptical teams that this isn't just noise but real ongoing debt reduction.
honestly this looks super useful, but one thing that would make me trust it even more is a dry run mode that shows the exact diff before anything gets pushed. like basically a sandbox preview so you can sanity check the rewrites against your real codebase without committing to a PR yet.
One thing I'd love to see is a dashboard view showing the "cleanup velocity" over time, like how many flags were flagged, reviewed, and merged per week. Right now the value feels invisible once the PRs land. Surfacing trends would really help convince skeptical teams that this isn't just noise but real ongoing debt reduction.