DEVOPS
Publish a monthly feature-flag debt report to Notion
Monthly, tallies total flags, how many are past kill-date, average overdue age, and per-team breakdowns from your code and Statsig.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionCollect flag refs and kill-dates from GitHubGitHub
- ActionPull last-evaluated data from Statsig APIHTTP webhook
- LogicCompute totals, overdue age, per-team breakdown
- ActionCreate dated report page in NotionNotion
- OutputPost report link to SlackSlack
What it does
Gives leadership a recurring scorecard on flag hygiene. It counts every flag in the codebase, cross-checks against Statsig for last-evaluated dates, and computes the metrics that matter: open flag count, number past kill-date, average days overdue, and a per-team ranking. It then publishes a clean, dated report page to Notion.
When to use it
When you want flag debt visible in the same place as other engineering health metrics, trending month over month. Good for staff meetings and sprint planning where someone asks "is our flag debt getting better or worse?"
How it works
- 1A monthly schedule triggers the run.
- 2The flow collects all flag references and kill-dates from GitHub and pulls last-evaluated data from the Statsig API.
- 3A logic step computes totals, overdue counts, average age, and per-team breakdowns.
- 4It creates a dated report page in Notion with tables and trend notes.
- 5It posts the Notion link to Slack so the team sees the new report.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.