deploymentlisted

# Purpose Orchestrate the project's service deployments across local-dev (Minikube), the staging environment (project.json → cloud.envAlias; typically a cloud VM + Minikube), and production (e.g. edge device + k3s) using Helm, producing a deploy status report with pod health and endpoint verification. This skill covers the single-environment deploy-and-verify cycle; it defers image building to `docker-build`, chart template authoring to `helm-chart-expert`, and cross-environment promotion to `release-promotion`. # When to use this skill - Trigger A -- Deploying a Helm release to any single project environment - Trigger B -- Running post-deployment verification (pod health, endpoint checks, ingress validation) - Trigger C -- Rolling back a failed Helm release within the same environment - Trigger D -- Inspecting current deploy state (helm list, helm history, pod status) # When NOT to use this skill - Anti-trigger A -- Building or pushing Docker images -> use `docker-build` instead - Anti-trigger B -- Writing or modifying Helm chart templates -> use `helm-chart-expert` instead - Anti-trigger C -- CI/CD pipeline configuration -> use `gitlab-ci-cd` instead - Anti-trigger D -- Production deploy without an approved merge request -> stop and escalate - Anti-trigger E -- Staging-environment operational recovery (SSH debugging, secret rotation, VM recovery) -> follow the project's environment runbooks; cluster-level pieces belong to `kubernetes-deployment` - Anti-trigger F -- Pro