deployment-automation▌
aj-geddes/useful-ai-prompts · updated Apr 8, 2026
Establish automated deployment pipelines that safely and reliably move applications across development, staging, and production environments with minimal manual intervention and risk.
Deployment Automation
Table of Contents
Overview
Establish automated deployment pipelines that safely and reliably move applications across development, staging, and production environments with minimal manual intervention and risk.
When to Use
- Continuous deployment to Kubernetes
- Infrastructure as Code deployment
- Multi-environment promotion
- Blue-green deployment strategies
- Canary release management
- Infrastructure provisioning
- Automated rollback procedures
Quick Start
Minimal working example:
# helm/Chart.yaml
apiVersion: v2
name: myapp
description: My awesome application
type: application
version: 1.0.0
# helm/values.yaml
replicaCount: 3
image:
repository: ghcr.io/myorg/myapp
pullPolicy: IfNotPresent
tag: "1.0.0"
service:
type: ClusterIP
port: 80
targetPort: 3000
resources:
requests:
memory: "256Mi"
cpu: "250m"
limits:
memory: "512Mi"
cpu: "500m"
autoscaling:
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Helm Deployment Chart | Helm Deployment Chart |
| GitHub Actions Deployment Workflow | GitHub Actions Deployment Workflow |
| ArgoCD Deployment | ArgoCD Deployment |
| Blue-Green Deployment | Blue-Green Deployment |
Best Practices
✅ DO
- Use Infrastructure as Code (Terraform, Helm)
- Implement GitOps workflows
- Use blue-green deployments
- Implement canary releases
- Automate rollback procedures
- Test deployments in staging first
- Use feature flags for gradual rollout
- Monitor deployment health
- Document deployment procedures
- Implement approval gates for production
- Version infrastructure code
- Use environment parity
❌ DON'T
- Deploy directly to production
- Skip testing in staging
- Use manual deployment scripts
- Deploy without rollback plan
- Ignore health checks
- Use hardcoded configuration
- Deploy during critical hours
- Skip pre-deployment validation
- Forget to backup before deploy
- Deploy from local machines
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★72 reviews- ★★★★★Aarav Iyer· Dec 20, 2024
deployment-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aarav Ghosh· Dec 20, 2024
Keeps context tight: deployment-automation is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ganesh Mohane· Dec 12, 2024
I recommend deployment-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Xiao Huang· Dec 12, 2024
deployment-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Min Johnson· Dec 12, 2024
I recommend deployment-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ira Farah· Dec 8, 2024
deployment-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amina Martinez· Dec 4, 2024
Useful defaults in deployment-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Xiao Park· Nov 27, 2024
deployment-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Harper Smith· Nov 23, 2024
I recommend deployment-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Xiao Kim· Nov 11, 2024
deployment-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 72