deploy

Automate code shipping and Kubernetes deployment across dev, staging, and prod.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill deploy-reliant-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/deploy
Command: npx skills add https://github.com/reliant-labs/forge --skill deploy-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying a service without confidence causes downtime, broken releases, and painful rollbacks. It provides a repeatable workflow that ensures code quality, builds consistently, deploys to the right environment, and verifies health afterward.

Core Features & Use Cases

  • Pre-flight checks: Enforces linting (including proto and contract checks) and requires tests to pass before shipping.
  • Build options: Produces binaries and can also build Docker images or build with debug symbols for troubleshooting.
  • Environment-aware deploy: Deploys to k3d local or staging/prod with dry-run manifest rendering and immutable image tagging.
  • Post-deploy verification + rollback guidance: Verifies pods and logs, and describes safe rollback behavior with rollouts.

Quick Start

Run forge deploy dev to lint, build, deploy to your local k3d environment, and verify the resulting pods.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate Kubernetes deployments across dev, staging, and prod environments?

Automate Kubernetes deployments by applying a CI-aligned workflow that lints code, builds images, generates environment-specific manifests, and verifies post-deploy pod health across dev, staging, and prod.

What is the safest way to roll back a broken Kubernetes deployment?

The safest rollback procedure uses kubectl rollout undo to revert to a previous stable state, ensuring deployment safety by enforcing immutable image tags and verifying pod health before and after releases.

Can I render and review Kubernetes YAML manifests before applying them to staging or prod?

Yes, you can review rendered YAML manifests using dry-run support before deploying to staging or prod, allowing you to inspect environment-specific configurations safely without applying changes.

How do I enforce linting and testing before building a Docker image for deployment?

Enforce linting and testing by integrating pre-flight checks that require Go, proto, and contract linting to pass alongside tests before building Docker images or binaries for deployment.

Does this deployment workflow support local k3d clusters for development testing?

Yes, the deployment workflow supports k3d local environments, allowing you to lint, build, deploy, and verify pods locally before pushing to staging or production environments.

Why should I use immutable image tags for Kubernetes deployments?

Immutable image tags ensure strict rollout safety by preventing accidental overwrites of existing images, providing reliable rollback procedures and consistent deployment tracking across environments.