version-release-protocol

Name: version-release-protocol
Availability: InStock
Author: come0520

Orchestrate a 7-step software release with quality gates and ECS deployment.

Updated Dec 1, 2025

Search Tags:#ci/cd #versioning #deployment #rollback #release #quality gate #ecs

Ready to run

npx skills add https://github.com/Come0520/L2C --skill version-release-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-release-protocol
Source: https://github.com/Come0520/L2C/tree/main/.agent/skills/version-release-protocol
Command: npx skills add https://github.com/Come0520/L2C --skill version-release-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized, 7-step protocol for releasing new software versions, ensuring quality, traceability, and safe deployment to production environments.

Core Features & Use Cases

Automated Quality Gates: Integrates multiple checks (build, lint, tests, security, API health) before deployment.
Version Management: Handles version bumping, commit, and push operations.
Deployment Orchestration: Guides through packaging, uploading, and deploying to ECS, including rollback procedures.
Use Case: When a developer is ready to deploy a new feature, they initiate this Skill to systematically verify the code, update version information, and execute a safe, documented deployment to the production servers.

Quick Start

Use the version-release-protocol skill to deploy the next patch version to production.

Frequently Asked Questions about version-release-protocol

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

FAQPage Schema

How do I automate a safe deployment to ECS with quality gates and rollback?▼

To automate ECS deployment, this protocol runs a 7-step release process with automated quality gates, version incrementing, artifact packaging, and production deployment, including rollback procedures to ensure stability.

What does a 7-step software release protocol include for version management?▼

A 7-step software release protocol includes automated quality checks, version number incrementing, contribution wall updates, code commits, local builds, artifact packaging, and deployment to production ECS servers.

How do I increment version numbers and update contribution walls before a production deployment?▼

You increment version numbers and update contribution walls during the protocol's initial steps before code commits and local builds, ensuring traceability and documentation for the production deployment.

Can I use this release protocol to roll back a failed ECS deployment?▼

Yes, you can use this release protocol to roll back a failed ECS deployment, as it manages rollback procedures and ensures production stability through rigorous post-deployment validation checks.

What automated quality checks are required before deploying to production servers?▼

Before deploying to production, the protocol requires automated quality gates including build, lint, tests, security, and API health checks to verify the code and ensure safe deployment.

When should I avoid using an automated release protocol for CI/CD?▼

You should avoid using an automated release protocol if your project lacks a structured ECS deployment target or if your workflow cannot accommodate a rigid 7-step versioning and quality gate verification process.