deploy-non-prod-ho

Automate Headout service deployments to test and ODE environments.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/sameer-thakkar/hackin26-next-deimos --skill deploy-non-prod-ho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-non-prod-ho
Source: https://github.com/sameer-thakkar/hackin26-next-deimos/tree/main/.cursor/skills/deploy-non-prod-ho
Command: npx skills add https://github.com/sameer-thakkar/hackin26-next-deimos --skill deploy-non-prod-ho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-actions, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages the deployment of Headout services to test and ODE environments, streamlining the process and ensuring accurate rollouts.

Core Features & Use Cases

  • Repo-aware Deployment: Automatically detects services from repository metadata and uses the current commit.
  • Explicit Deployment: Allows manual specification of service name and commit for precise deployment.
  • ODE Management: Lists, creates, deletes ODEs, checks status, scales up dormant environments, and shares access.

Quick Start

Deploy your current branch to the test environment using the alias 'deploy-non-prod-ho --env test'.

Frequently Asked Questions about deploy-non-prod-ho

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

FAQPage Schema
How do I deploy Headout services to a test environment using my current branch?

Deploy Headout services to a test environment using the alias 'deploy-non-prod-ho --env test'. The Skill automates repo-aware deployment by detecting services from repository metadata and deploying the current commit automatically.

Can I manually specify a service name and commit for ODE deployment?

Explicit deployment allows manual specification of service name and commit for precise ODE deployment. This ensures accurate rollouts when repo-aware automatic detection does not fit your specific service management requirements.

What ODE lifecycle operations are supported for test environment management?

ODE management supports listing, creating, deleting ODEs, checking status, scaling up dormant environments, and sharing access. These operations provide full lifecycle control over test and ODE environments.

Do I need shell access to configure environments for Headout service deployment?

Shell access is required for alias setup and specific environment configurations. Git and GitHub Actions dependencies are also necessary to automate the deployment of Headout services to test and ODE environments.

What is the best way to scale up dormant ODE environments?

Scaling up dormant ODE environments is handled natively through the ODE management operations. The Skill checks status and scales up dormant environments automatically, ensuring test environments are active when needed.