setup-deploy

Name: setup-deploy
Availability: InStock
Author: lapagayo

Configure Nexus deployment settings and write the deploy contract to .planning/deploy/.

1|Updated Mar 31, 2026

Search Tags:#automation #multi-platform #deploy #contracts #health-checks #nexus #land-and-deploy

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure deployment settings for Nexus across multiple platforms, ensuring consistent deployment contracts and automation for future deploys.

Core Features & Use Cases

Detects the target deployment platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) and production URL, including health check endpoints.
Writes the canonical deploy contract to .planning/deploy/ so all future deploys run automatically.
Supports common Nexus commands like /deploy and /land-and-deploy and helps teams standardize deployment workflows across environments.

Quick Start

Run the Nexus deployment configuration flow to detect your platform and generate the canonical deploy contract.

Frequently Asked Questions about setup-deploy

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

FAQPage Schema

How do I configure automated multi-platform deployment contracts for Nexus?▼

This deployment configuration flow detects your target platform, production URL, and health check endpoints, then writes a canonical deploy contract to .planning/deploy/ so future deploys run automatically and consistently.

What deployment platforms are supported by the Nexus land-and-deploy configuration?▼

Supported deployment platforms include Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom platforms, allowing Nexus to detect and configure deployment settings across multiple environments.

How do I set up health checks for automated deployments across different environments?▼

The deployment configuration flow detects health check endpoints alongside production URLs across environments and writes them into the canonical deploy contract stored in .planning/deploy/.

Can I use Nexus land-and-deploy commands with GitHub Actions for deployment automation?▼

Yes, GitHub Actions is detected as a supported deployment platform during the configuration flow, enabling you to standardize deployment workflows and use commands like /deploy and /land-and-deploy for automated releases.

What's the best way to standardize deployment workflows across multiple platforms?▼

Standardize deployment workflows by generating a canonical deploy contract in .planning/deploy/ that detects your specific platform, production URL, and health checks, ensuring all future deployments run automatically with consistent settings.

Do I need a custom platform configuration if my deployment target isn't listed?▼

No, the deployment configuration flow supports custom platform detection, allowing you to define a canonical deploy contract in .planning/deploy/ even if your specific deployment target isn't among the standard pre-listed platforms.