Find and flag unused feature flags in your Android codebase

Old, unused feature flags in your code are found weekly and turned into tracked cleanup tickets automatically.

How the work actually flows

It branches. Every path runs.

Pattern: Sequence (1) ยท Parallel Split (2)

flowchart TD trig(["weekly scan schedule"]):::trigtime s0["scan repo for feature flags"]:::svc s1["compare against flag management tool"]:::svc s2["mark unused flags dead"]:::task s3[("log results to spreadsheet")]:::store trig --> s0 s0 --> s1 s1 --> s2 s2 --> s3 gx{"+ notify and track cleanup"}:::gate s3 --> gx p00["open ticket per flag"]:::task gx -->|"create cleanup ticket"| p00 p10["post slack alert"]:::task gx -->|"alert team"| p10 p00 --> out p10 --> out out[/"dead flags identified and ticketed"/]:::out pay{{"cleaner codebase with less manual auditing"}}:::pay out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceA record or sheetEvery pathResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
Messaging & NotificationsSpreadsheet & Database OpsProject & Task ManagementDevOps & IT Operations
Connects
GitLabLaunchDarklyGoogle SheetsJiraSlack

The problem it solves

Feature flags pile up in your codebase long after they've served their purpose, quietly adding complexity and risk. Nobody has time to hunt through the code and your flag management tool to figure out which ones are safe to remove.

Who it fits

Android engineering and DevOps teams managing feature flags at scale.

How it works

  1. Every week, the system scans your code repository for feature flags
  2. It compares that list against your feature flag management tool
  3. Flags that are unused in code and turned off in production are marked dead
  4. Results are logged to a spreadsheet
  5. A cleanup ticket is created and your team gets a Slack alert
What you get

Stale flags spotted before engineers waste time

You get a weekly list of forgotten feature flags with a ready-made cleanup ticket, so your engineering team can keep the codebase tidy.

What you get

A logged list of dead feature flags, a cleanup ticket for each, and a team notification.

What you need

A GitLab account, a LaunchDarkly account, Google Sheets, Jira, and a Slack workspace.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Create Jira incidents and alert your on-call team in Slack

Creates a Jira ticket, alerts your on-call team in Slack, and files a timestamped report the moment an incident starts.

Advanced

Get alerted the moment a new threat hits your tech stack

Scans threat feeds hourly, matches them to your systems, and alerts your team before attackers can exploit them.

Advanced

Automatically rate the risk of every dependency update ticket

AI reviews new Jira dependency tickets, rates the risk, and alerts your team in Slack automatically.

Advanced

Monitor website uptime and log incidents in Jira and Sheets

Checks your website on a schedule and automatically opens a Jira ticket, alerts Slack, and logs downtime.

Standard
Back to the AI Playbook