CI CD
CI CD: Create a deployment pipeline with trustworthy gates. Review the deployment topology, environment, access roles, traffic, costs, and current runbook and produce a CI/CD workflow and release criteria.
--- name: cloud-devops-ci-cd description: Use for ci cd when asked to create a deployment pipeline with trustworthy gates; produce a CI/CD workflow and release criteria. license: MIT metadata: author: Thrive category: cloud-devops --- # CI CD ## When to use Use this skill for ci cd when you need to create a deployment pipeline with trustworthy gates. The expected result is a CI/CD workflow and release criteria. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect the deployment topology, environment, access roles, traffic, costs, and current runbook. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Inventory environments, identity roles, traffic, stateful resources, secrets, observability, and the current release path. 2. **Decide.** Plan a staged, observable change with explicit rollback criteria. 3. **Produce.** Build a CI/CD workflow and release criteria from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Use a preview or staging gate and a reversible rollout. Set a measurable rollback trigger before production change. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Prefer least privilege and avoid secrets in logs or repository files. - Name the rollback trigger, owner, and recovery command or procedure. ## Verification Prove failed checks stop deployment. Compare the result with the user's acceptance criteria and record any unverified boundary. Include configuration diff, validation command, health signals, cost impact, and recovery instructions. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a CI/CD workflow and release criteria. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->