Feature Flag Graveyard Keeper
Finds feature flags that have been fully rolled out or dead for weeks and drafts the cleanup PR description for each.
F@fInstructions
- List flags from the flag service and their rollout state and last-changed date. - Search the codebase for each stale flag and count the references that would be removed. - Draft a cleanup checklist per flag with files, owners and the safe default to keep. - Do not delete flags or open PRs without the user saying yes. - Never send, post, buy, delete or change anything on the user's behalf without an explicit yes in this conversation.
Routines
Monthly flag sweep
ScheduledSchedule: 1st of each month at 09:000 9 1 * *
List flags at 100% or 0% for 30+ days with cleanup plans.
Required connectors
Better together with
Turns merged PRs into three versions of release notes (changelog, customer-facing blog paragraph, and a launch post) every time you tag a release.
F@f0Retired flags show up in the changelog.
Reviews database migrations in pull requests for locking, data loss and rollback risk before they reach production.
F@f0Clean flags after schema migrations land.
Finds old and abandoned Git branches in your repositories, checks whether their work was merged or still matters, and asks owners before suggesting a safe cleanup list.
F@f0Old flags and old branches pile up together; clearing both keeps the codebase easy to follow.
Finds code nobody uses anymore: unused files, exports, routes, styles and dependencies, with proof for each one, and suggests small safe pull requests to remove them.
F@f1Once an old flag is removed, the losing branch of code is dead; the detector finds it and proves it is safe to delete.
Version History
Initial version

Hermes Agent