Verify pre-deployment gates and post-deploy SLO health for production releases.
npx skills add https://github.com/PiercingXX/xx-stack --skill deploy-ship-piercingxx
Please help me install this Agent Skill. Skill: deploy-ship Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/deploy-ship Command: npx skills add https://github.com/PiercingXX/xx-stack --skill deploy-ship-piercingxx
It prevents risky or incomplete production releases by forcing a repeatable deployment checklist that verifies tests, build/artifacts, changed scope, and post-deploy health.
Tell the skill to run the production release checklist for this repository and produce a Deployment Report including the pre-check results, the actual release path used, and the required health-check outcomes.
High-intent search queries and answers about installing and using this skill.
Production deploy readiness is verified by enforcing deterministic pre-deployment gates that validate CI checks, build artifacts, and change scope via git diff analysis. A release checklist confirms all tests pass before any deployment step is executed.
A post-deploy SLO smoke window monitors operational health metrics like error rate, latency, throughput stability, and auth success after deployment. If SLO thresholds are exceeded, it triggers rollback recommendations to prevent prolonged production issues.
For repositories with no deploy surface, the release checklist validates only repo-supported release paths and skips invented deploy routes. It still enforces pre-deployment gates, CI verification, and git diff analysis to assess change scope before packaging or publishing.
Yes, rollback recommendations are generated automatically when post-deploy health checks exceed defined SLO thresholds. The system monitors error rate, latency, and throughput stability during the smoke window to decide whether to continue monitoring or trigger a rollback.
Hard quality gates are enforced by applying a repeatable deployment checklist that validates CI results, build readiness, and change size via git diff and log review. Deployment execution only proceeds through repo-supported paths, avoiding risky or incomplete releases.
An automated deployment checklist may not suit workflows where the repository exposes no supported release path or where custom deployment routes are required. It validates only repo-supported paths and will not invent deploy surfaces that the repository does not explicitly provide.
SpineEventEngineRun repository pre-pull-request version, build, and reviewer checks.
andregusman-raizMonitor production health after deployment and automate rollback decisions.
oalansilvaDefine and enforce performance budgets across CI/CD pipelines.
wednesday-solutionsVerify pre-deploy prerequisites and post-deploy health for production deployments.
