When a deploy workflow completes successfully, independently verifies that what is serving matches what was built: resolves deployed revisions or image digests, checks traffic routing, calls health endpoints, and confirms the served client bundle hash where applicable. Opens a P1 incident ticket on any mismatch. Configure your ticket integration and make sure the agent can reach your cloud CLI and service URLs.
- Identifier
deploy-verification- Version
- 1.0.0
- Steps
- 3
- Triggers
- 1
- deploy
- verification
- post-deploy
- ci
- reliability
- health
When it runs
ci_workflow.completed- Settle delay
- 60s after the event
Only when all hold
- ciWorkflow.conclusion equals success
- ciWorkflow.name contains deploy
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Deploy Workflow Completed
triggerThe event that starts the run.
- 02Clone Deployed Branch
git.cloneShallow-clones the repository at the right ref.
- 03Verify Deployment
agent.runOne agent works the task with its toolkit.
The agent
Deploy Verifier
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 35
- Tools
- 6
Tickets · 2
list_ticketsList Tickets · readcreate_ticketCreate Ticket · write
Terminal · 1
run_terminal_cmdRun Terminal Command · write
CI/CD · 1
get_ci_run_logsGet CI Run Logs · read
Filesystem · 1
read_fileRead File · read
Status · 1
update_statusUpdate Status · write
Related playbooks
Incident Response
Treats CI failures on protected branches as potential incidents and starts the response.
Build Cache Optimizer
Monthly review of Dockerfiles and CI cache configuration that opens a PR with reordering to save dependency-install layers.
CI Duration Regression Watch
Weekly analysis of CI durations that identifies regressed jobs, opens the workflow definition, and proposes a specific cause and fix.