deploy

Deploy built artifacts to dev, staging, or production with dry-run and health checks.

Updated Dec 21, 2018
One-click install
npx skills add https://github.com/dhnt/dhnt --skill deploy-dhnt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/deploy/deploy
Command: npx skills add https://github.com/dhnt/dhnt --skill deploy-dhnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or unsafe releases by guiding you through a disciplined deploy workflow with explicit pre-flight checks, dry-runs, and post-deploy verification.

Core Features & Use Cases

  • Environment-appropriate deployment: chooses the correct target (dev, staging, or prod) and deploy mechanism without inventing new processes.
  • Safer execution with validation: performs dry-runs when available and validates artifacts and CI status before rollout.
  • Operational verification: waits for readiness via health checks and smoke tests, then records the outcome in the project’s conventions.

Quick Start

Tell the agent which environment you want to deploy to (dev, staging, or prod) and what deploy mechanism and artifact/tag should be used, and ask it to run the safest available dry-run, apply the change, verify health and smoke tests, and update the deploy log or changelog.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I safely deploy an artifact to staging or production?

To safely deploy an artifact, you can guide the workflow by selecting the target environment, validating CI status and authorization, running a dry-run, applying the change via kubectl or make targets, and verifying health checks.

What pre-flight checks are needed before a production rollout?

Essential pre-flight checks for a production rollout include validating the built artifact, confirming authorization status, verifying CI pipelines, and executing an optional dry-run to minimize release risk and prevent broken deployments.

How do I verify readiness after a kubectl deployment?

You verify readiness after a kubectl deployment by waiting for health checks to pass and executing smoke tests to ensure the new release is operating correctly before recording the outcome in the project deploy log.

Can I use infrastructure as code to trigger CI/CD deployments to dev?

Yes, you can use infrastructure as code and CI/CD triggers to deploy to dev, staging, or prod by following environment selection rules and applying changes through your chosen deployment mechanism.

What is the best way to minimize release risk when shipping to prod?

The best way to minimize release risk is to follow a disciplined deploy workflow that includes explicit pre-flight artifact validation, dry-run execution, streamed rollout, and post-deploy health and smoke testing.

Why does my deployment fail health checks after a CI/CD rollout?

Deployments fail health checks when the built artifact is not fully ready; waiting for readiness verification via health checks and smoke tests after applying the change helps detect and prevent broken releases.