DEVOPS
Agent rewrites an over-budget BigQuery query and opens a tuning PR
When a query is flagged over budget, an agent inspects the SQL and table partitioning, drafts a cheaper rewrite, opens a GitHub PR with the proposed diff, and links it in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerOver-budget query flagged
- ActionRead query and table partitioning in BigQueryBigQuery
- LogicDraft rewrite and dry-run to confirm savings
- ActionOpen GitHub PR with proposed diffGitHub
- OutputLink the PR on the Linear taskLinear
What it does
This goes beyond flagging. When a query is identified as over budget, an agent reviews the SQL alongside the referenced tables' partitioning and clustering, then drafts a lower-cost rewrite, for example adding a partition filter or pruning a SELECT *. It opens a GitHub pull request with the proposed change and a dry-run cost comparison, then links the PR on the originating Linear task.
When to use it
Use it when your team has more flagged queries than time to fix them and you want a reviewable first draft of the optimization rather than just a ticket. A human still approves the PR.
How it works
- 1A flagged over-budget query event triggers the flow.
- 2The agent reads the query and the referenced tables' schema and partitioning in BigQuery.
- 3The agent drafts a cheaper rewrite and dry-runs it to confirm the savings.
- 4A GitHub PR is opened with the rewrite and a before/after cost note.
- 5The agent comments the PR link on the related Linear task for review.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.