ENGINEERING
Daily GitLab coverage trend Slack digest
Runs each morning, computes per-repository coverage trend from stored pipeline history, and posts a Slack digest ranking the repos with the biggest weekly coverage drops.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionQuery 7-day coverage historyPostgres
- LogicCompute per-repo deltas and rank
- OutputPost trend digest to SlackSlack
What it does
On a daily schedule this workflow reads the coverage history captured from GitLab MR and default-branch pipelines, calculates each repository's seven-day coverage change, and sends an engineering channel a Slack digest. The digest leads with the repos losing the most coverage so leads can act before regressions compound.
When to use it
Use it when individual MR gates are not enough and you want an org-wide view of where test coverage is eroding over time. Good for engineering managers running a weekly quality review or anyone who wants a standing health signal without opening each project.
How it works
- 1A scheduled trigger fires every weekday morning.
- 2The flow queries Postgres for the last seven days of per-repo coverage points recorded from pipelines.
- 3It computes each repo's start-to-end delta and current absolute coverage.
- 4A logic step ranks repos by largest negative delta and flags any below the floor.
- 5It formats the ranked table and posts it to the engineering Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.