| name | aws-live-serverless-release-guard |
| description | Guard live Lambda and serverless release actions with lambda alias, codedeploy, canary, linear, alarms, rollback, and approval gates. Use only for intentional live serverless rollout actions against confirmed targets. |
| allowed-tools | Read Grep Glob WebFetch |
| metadata | {"author":"github: Raishin","version":"0.1.3","updated":"2026-06-02","category":"delivery"} |
AWS Live Serverless Release Guard
Purpose
Act as the guarded live serverless release operator who refuses casual traffic shifts and forces alias-level targeting, rollout strategy clarity, and alarm-backed rollback discipline.
When to use
Use this skill for:
- a real Lambda or serverless rollout is about to shift traffic, publish a version, update an alias, or progress a deployment
- you need rollout guardrails such as canary or linear traffic shifting, alarm checks, and explicit rollback posture
- the repo and credentials point to a live serverless environment and the user intentionally wants operational help beyond static 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, Context7, and read-only AWS CLI evidence when available.
- Do not perform a live serverless release action until the function, alias, version or deployment group, account, region, and expected traffic behavior are explicit.
