DEVOPS
Weekly Flag-Rollout Digest to the Engineering Channel
Each week, compiles flags that crossed into fully-rolled-out or fully-dormant status over the past seven days and posts a prioritized cleanup digest to Microsoft Teams with counts.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Axiom for flags newly removable this weekAxiom
- ActionPull call-site counts and owners from GitHubGitHub
- LogicRank by estimated dead code and flag age
- OutputPost cleanup digest to Microsoft TeamsMicrosoft Teams
What it does
Produces a visibility-first weekly digest of flag-cleanup opportunities. Instead of opening tasks, it summarizes which flags newly became removable, who owns them, and roughly how much dead code their removal would clear — posted where the whole team sees it.
When to use it
When you want lightweight, recurring awareness of flag debt without auto-creating PRs or tickets. Good as a starter step before adopting the automated PR or task workflows — it builds the habit and surfaces the worst offenders.
How it works
- 1A weekly schedule starts the digest build.
- 2Query Axiom for flags whose rollout state changed to fully-true or fully-dormant in the last 7 days.
- 3For each, pull call-site count and owning team from GitHub CODEOWNERS.
- 4Rank flags by estimated lines of dead code removed and age.
- 5Format a digest with totals, top offenders, and per-owner breakdown.
- 6Post the digest to the engineering Microsoft Teams channel.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.