tag-based-production-deploys

Enforce git tag-based production deployments with manual approval gates.

28|3|Updated Feb 22, 2026

Search Tags:#automation #ci/cd #deployment #production #git tags #terraform #approval gates

Ready to run

npx skills add https://github.com/oborchers/fractional-cto --skill tag-based-production-deploys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tag-based-production-deploys
Source: https://github.com/oborchers/fractional-cto/tree/main/cloud-foundation-principles/skills/tag-based-production-deploys
Command: npx skills add https://github.com/oborchers/fractional-cto --skill tag-based-production-deploys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill prevents accidental production deployments by enforcing a strict separation between development and production release processes, ensuring every production change is deliberate and auditable.

Core Features & Use Cases

Environment Separation: Automatically deploys to development on code push, but requires explicit git tags for production.
Auditable Releases: Uses git tags as immutable, traceable triggers for production deployments.
Approval Gates: Implements mandatory manual approval steps before any production infrastructure changes are applied.
Use Case: When deploying infrastructure changes, this skill ensures that a developer must create a git tag and pass a manual review before the changes are applied to the production environment, preventing costly mistakes.

Quick Start

Use the tag-based-production-deploys skill to set up a CI/CD pipeline that deploys to production only when a git tag is created.

Frequently Asked Questions about tag-based-production-deploys

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

FAQPage Schema

How do I prevent accidental production deployments in a CI/CD pipeline?▼

Prevent accidental production deployments by enforcing a strict separation between development and production release triggers, requiring explicit git tag creation and manual approval gates before any infrastructure changes are applied.

How do I set up a CI/CD pipeline that deploys to production only when a git tag is created?▼

Set up a CI/CD pipeline that deploys to production only when a git tag is created by configuring environment separation, mandating git tags as immutable triggers, and incorporating manual approval gates before applying changes.

Why use git tags for production deployments instead of pushing code directly?▼

Use git tags for production deployments to create immutable, traceable triggers that ensure every production change is deliberate and auditable, preventing costly mistakes associated with direct code pushes.

Can I use manual approval gates with Terraform for production infrastructure changes?▼

Yes, you can implement manual approval gates with Terraform to mandate manual review steps before any production infrastructure changes are applied, ensuring secure and auditable deployment workflows.

What are the limitations of using git tags for production release triggers?▼

Using git tags for production release triggers requires strict adherence to the full pipeline flow from commit to verified release, meaning any bypass of the manual approval gates or pre-commit hooks compromises the deployment audit trail.