Pre-deploy release gatekeeper agent
Custom agent: The author built SHIPCHECK, a ReAct agent that queries a Sanity Content Lake over MCP to check whether a service upgrade is safe before deploy.
On a payment service v2 to v4 test, it caught an outdated SDK, returned DO NOT SHIP YET, then SAFE TO SHIP in simulation.
Overview
How it was set up
Custom ReAct agent using Sanity Content Lake with GROQ queries, exposed through four typed MCP tools. Documents encode components, version constraints, and authority-weighted knowledge entries.
Worth knowing
Demo runs against a purpose-built Sanity dataset; the source does not show it gating a real production deployment.
A prompt to start from
Can I upgrade [service] from [current version] to [target version] in [environment] tonight? Check version constraints, live cluster dependencies, and conflicting docs, then give a ship or no-ship verdict with remediation steps.
Written by Agentic Feats from the source. Not the author's exact prompt.
Sources 1
History
- Source published
- 2026-09-26
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/pre-deploy-release-gatekeeper-agent-custom-agent.md
More in ops and IT
20 featsResultProvisioning worked after two fixes. The MCP hid the real errors, so apply ran through Cursor's Run tool, which suggested the fix.
ResultThe author migrated 10+ Lambda functions from Node.js 14 to 20 in one pass and fixed a broken docker-compose file by auto-retrying until clean.
ResultThe author runs 14 containers including Vaultwarden, Immich, Plex, and Readeck, with daily USB and weekly S3 Glacier backups costing about twenty cents per month.