Problem
What problem this solves
A deploy can succeed mechanically while the live product is still unhealthy, broken, or misconfigured.
Skill Detail
Check whether production is actually healthy after a push instead of assuming the deploy tells the truth.
A production verification skill for deployment status, logs, and live health checks after release.
Problem
A deploy can succeed mechanically while the live product is still unhealthy, broken, or misconfigured.
Outcome
You get a stronger post-release confirmation that production is behaving as expected.
Why It Matters
This skill matters because shipping is not finished when the command exits. It is finished when production actually works.
Related Skills
Use one explicit technical mode for code risk, dependencies, performance, or a breaking migration.
A unified technical entrypoint with four bounded modes and evidence limits that match the work.
Open skill pageCommit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageRun the standard technical checks and fix the obvious issues before you pretend the work is done.
A practical quality gate for typecheck, lint, build, and related technical validation in the current project.
Open skill pageOpen a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill pageTriage a bug fast, decide whether it is safe to patch now, and route it correctly.
The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.