deploy

Name: deploy
Availability: InStock
Author: lapagayo

Automate end-to-end deployment workflows with health checks and release gating.

1|Updated Mar 31, 2026

Search Tags:#workflow #deployment #production #governance #deploy #health-check #ci_cd

Ready to run

npx skills add https://github.com/LaPaGaYo/nexus --skill deploy-lapagayo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/deploy
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill deploy-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end deployment workflow that follows a PR landing, ensuring production readiness through deploy contracts, production URLs, and health checks.

Core Features & Use Cases

End-to-end deployment orchestration after PRs land across environments.
Enforces governance, validation, and release gating to prevent regressions.
Works with Nexus-managed surfaces; ensures deterministic execution and post-deploy checks.

Quick Start

Run the deploy skill after a PR lands to push the change to production, verify health, and gate the release.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate the deployment workflow after a pull request is merged?▼

Automating the deployment workflow after a PR lands is handled by orchestrating the end-to-end release across environments. This process pushes changes to production, verifies health checks, and applies release gating to prevent regressions.

What is the best way to enforce release gating and governance for production deployments?▼

Enforcing release gating for production deployments requires applying stage manifests and health signals during the release process. This ensures deterministic execution and validates post-deploy health to prevent unauthorized regressions.

How do production health checks work during automated deployment?▼

Production health checks during deployment validate the release by monitoring health signals after changes are pushed. This post-deploy validation ensures the environment remains stable and gates the release against potential failures.

Can I use this deployment orchestration for non-production environments?▼

This deployment orchestration applies to end-to-end workflows across environments, not just production releases. It coordinates deploy contracts and URLs for merged changes wherever deterministic execution and validation are required.

Why do I need deploy contracts and stage manifests for CI/CD pipelines?▼

Deploy contracts and stage manifests are needed for CI/CD pipelines to ensure deterministic execution and governance. They coordinate production URLs and health checks, preventing regressions by strictly validating each release stage.

When should I not use automated deployment orchestration for my release?▼

Automated deployment orchestration should not be used when your release requires manual intervention outside of stage manifests and health signals. It enforces deterministic execution and governance workflows, limiting ad-hoc manual deployments.