<< All versions

Skill v1.0.0

currentAutomated scan100/100
aj-geddes/useful-ai-prompts/deployment-documentation
──Details
PublishedOctober 1, 2026 at 12:22 AM
Content Hashsha256:e1b1f05c76b173b2...
Git SHA3f5182cfd739
──Files
Files (1 file, 2.3 KB)
SKILL.md2.3 KBactive
SKILL.md · 103 lines · 2.3 KB

version: "1.0.0" name: deployment-documentation description: > Document deployment processes, infrastructure setup, CI/CD pipelines, and configuration management. Use when creating deployment guides, infrastructure docs, or CI/CD documentation.


Deployment Documentation

Table of Contents

Overview

Create comprehensive deployment documentation covering infrastructure setup, CI/CD pipelines, deployment procedures, and rollback strategies.

When to Use

  • Deployment guides
  • Infrastructure documentation
  • CI/CD pipeline setup
  • Configuration management
  • Container orchestration
  • Cloud infrastructure docs
  • Release procedures
  • Rollback procedures

Quick Start

Minimal working example:

`markdown
# Deployment Guide
## Overview
This document describes the deployment process for [Application Name].
**Deployment Methods:**
- Manual deployment (emergency only)
- Automated CI/CD (preferred)
- Blue-green deployment
- Canary deployment
**Environments:**
- Development: https://dev.example.com
- Staging: https://staging.example.com
- Production: https://example.com
---
## Prerequisites
### Required Tools
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
GitHub Actions WorkflowGitHub Actions Workflow
DockerfileDockerfile
docker-compose.ymldocker-compose.yml
Deployment ManifestDeployment Manifest

Best Practices

✅ DO

  • Use infrastructure as code
  • Implement CI/CD pipelines
  • Use container orchestration
  • Implement health checks
  • Use rolling deployments
  • Have rollback procedures
  • Monitor deployments
  • Document emergency procedures
  • Use secrets management
  • Implement blue-green or canary deployments

❌ DON'T

  • Deploy directly to production
  • Skip testing before deploy
  • Forget to backup before migrations
  • Deploy without rollback plan
  • Skip monitoring after deployment
  • Hardcode credentials
  • Deploy during peak hours (unless necessary)
All versions