You were out for a few days. A deploy went out, SHAs moved, a couple of things shipped. What actually changed? /dev-whats-changed answers the catching-up question with three ordered layers — code that’s live, commits since the last release, and only then a deeper dive — so the story leads with cause, not with infra alerts.
We built 22 slash commands for our own workspace. This series walks through the ones we use most, starting with how we decide whether to ship a release.
We run /mgr-release-readiness before every release. Here is what it checks, how it works, and what it told us today — with live results from our actual environment.
Drop into the same workspace our team uses every day. Real clusters, real agents, real remediations. No sandbox. About 45 minutes.
