Deploy risk scan
Pre-flight a release — surface risky PRs, untested critical paths, and stop-ship candidates before deploy goes out.
Eluu — deploy-risk-scan
Shown in preview 
Runtime ~4 min per run
Tokens ~14K per run
Owner an eng release manager
Works with
Pick whichever tool your team already uses.
- Messaging Slack
Teams - PM / Tickets Linear
Jira 
Asana - Source control GitHub
GitLab
What it does
Pre-deploy checklists rarely catch the actual risks — half the team is gone for the weekend, and the release manager is reading 30 PR titles to guess. This recipe runs before each release, scores every PR by risk, surfaces stop-ship candidates (unsafe migrations, untested critical paths), and posts a brief so the release goes out informed.
How it works
- Pull merged PRs. Every PR merged since the last release tag is pulled with author, changed files, and review status. DB migrations / config changes / critical-path edits get detected.
- Analyze risk. Each PR is risk-scored (criticality × test coverage). Stop-ship candidates (unsafe migrations, missing tests in critical paths) get flagged. PRs link to Linear tickets. Auto-suggested rollback hooks surface.
- Post. Risk brief posts to #releases; authors of stop-ship candidates get DM’d; release manager tagged on critical findings.
Setup
- Connect a VCS tool (GitHub or GitLab).
- Connect a PM/tickets tool (Linear, Jira, or Asana).
- Connect a messaging channel (Slack or Teams).
Variations
- Auto-block a release if any stop-ship candidate is unaddressed.
- Run per-service risk briefs for monorepos.
- Generate a rollback playbook tailored to the riskiest PRs.
