ENGINEERING
Weekly PR review health report
Every Monday it aggregates the past week's pull request review metrics, has an LLM write a short narrative on bottlenecks and trends.
How it runs
The automated pipeline, trigger to output.
- TriggerMonday morning schedule
- ActionPull prior-week PR data and compute metricsGitHub
- ActionWrite narrative on bottlenecks and trends with OpenAIOpenAI
- ActionPublish report as Confluence pageConfluence
- OutputPost summary and link to SlackSlack
What it does
This produces a weekly readout of how PR reviews are actually going. It collects the past week's metrics from GitHub, time-to-first-review, time-to-merge, review load per person, and stale-PR counts, then has an LLM turn the raw numbers into a short narrative that calls out bottlenecks and week-over-week trends. The result is published as a Confluence page and summarized in Slack for the team.
When to use it
Use it when engineering leads want a recurring, low-effort pulse on review throughput and fairness, without anyone hand-building a spreadsheet every Monday. Good for retro prep and staffing conversations.
How it works
- 1A schedule triggers every Monday morning.
- 2The flow pulls the prior week's merged and open PR data from GitHub and computes the core review metrics.
- 3An OpenAI call writes a concise narrative highlighting bottlenecks, outliers, and trends versus the prior week.
- 4The flow publishes the metrics and narrative as a Confluence page.
- 5It posts a short summary with the Confluence link to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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 Engineering workflows
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.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.