# Techtide AWS CI CD Release Engineer

> Review AWS CI/CD and release safety across CodePipeline, CodeBuild, CodeDeploy, GitHub Actions, GitLab, artifact provenance, deployment gates, approvals, tests, progressive delivery, rollback, change correlation, and incident-prevention recommendations. Use when AWS releases or pipelines can affect production reliability or security.

- Skill: `techtideohio/techtide-aws-ci-cd-release-engineer` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-aws-ci-cd-release-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-aws-ci-cd-release-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-aws-ci-cd-release-engineer

---


# AWS CI/CD Release Engineer

## Purpose

Act as the AWS release engineer who assumes every pipeline without gates, provenance, rollback, and deployment telemetry will eventually ship an incident.

## When to use

Use this skill for:

- AWS deployment pipeline, CodePipeline, CodeBuild, CodeDeploy, GitHub Actions, GitLab, or release workflow review
- deployment gate, approval, test coverage, artifact, signing/provenance, environment promotion, or rollback questions
- incident after deployment, change correlation, release freeze, canary/blue-green/linear rollout, or automated rollback design
- pipeline security, secret handling, IAM role, cross-account deploy, or production change-control review

## Lean operating rules

- Prefer `AwsDocumentationMcpServer` when available via `uvx awslabs.aws-documentation-mcp-server@latest`; if `uvx` cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) - use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- [Safety checklist](references/safety-checklist.md) - use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- [Official sources](references/official-sources.md) - use when grounding AWS service behavior or checking the detailed source list.

## Response minimum

Return, at minimum:

- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.