DEVOPS
Block PRs that add flags with a missing or already-expired kill-date
On every pull request, checks any newly added feature flags for a valid future kill-date and posts a blocking review comment if a flag has no kill-date or one that's already…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- ActionFetch PR diff and extract newly added flagsGitHub
- LogicValidate each flag has a future kill-date
- ActionPost requested-changes review on failuresGitHub
- OutputSet pass/fail commit status on the PRGitHub
What it does
Stops new flag debt at the door. When a PR opens, it inspects the diff for newly introduced feature-flag references and verifies each one carries a `@kill-date` annotation set to a future date. Flags missing the annotation, or born already expired, get called out in a PR review that fails the check.
When to use it
When you want to enforce a flag-hygiene policy without manual review nagging. It guarantees every flag enters the codebase with a planned expiry, so the scanning janitor downstream always has a date to act on.
How it works
- 1A GitHub pull-request event triggers the run.
- 2The flow fetches the PR diff and extracts flag keys added in this change.
- 3A logic step validates each new flag: annotation present, date parseable, and in the future.
- 4If any flag fails, it posts a requested-changes review listing the offending flags and the policy.
- 5It sets the commit status to pass or fail so the merge gate reflects the result.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.