ADD Deploy Skill v0.5.0

Environment-aware deployments are orchestrated by loading configurations, selecting a target environment, and applying safety checks before committing, pushing, and triggering CI/CD workflows. This ensures safe, auditable software releases across local, dev, staging, and production.

Gated production approvals are enforced by applying environment-specific safety checks during deployment orchestration. This prevents unverified commits from reaching production by requiring explicit verification and approval checks before promoting code to the production environment.

A session handoff check verifies session continuity before committing and pushing code during deployment orchestration. It ensures the current development session meets required criteria before allowing the environment-aware commit, push, and deploy process to proceed.

Yes, multi-environment promotion ladders require loading configurations from a `.add/config.json` file. This configuration drives the environment selection, auto-promote rules, and rollback planning necessary for orchestrating safe releases across dev, staging, and production.

Yes, deployment verification and rollback planning are supported within AI-assisted development workflows. The orchestration process triggers CI/CD verification checks and supports promotion ladders with rollback planning to ensure safe, auditable software releases.

Auto-promote rules should not be used when gated production approvals are required for strict safety and auditability. If your software release demands manual verification before advancing between staging and production, disable auto-promote to enforce explicit environment checks.