Menu
Use the correct AWS CLI profile when running AWS commands based on the target environment.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Analyze code changes between two local Git branches and perform a comprehensive code review. Use ONLY for local git branch comparisons. Do NOT use when a GitLab or GitHub MR/PR URL or MR ID is provided — use gitlab-cli or github-cli skill instead.
Analyze code changes to prepare conventional commit message and commit to a new branch.
Create optimized, secure, production-ready Dockerfiles based on user requirements and application context.
Create a new SKILL.md file based on a guided conversation about a task or workflow.
Create a detailed upgrade plan for a Helm release managed by Terraform, comparing the current and desired chart versions including breaking changes and required code changes.
Perform GitHub operations on GitHub using the gh CLI. Use for issues, pull requests, pipelines, repositories, and project management. ALSO use this skill when asked to review a GitHub PR — when a GitHub PR URL or PR ID is provided, use gh to fetch and review the diff instead of the code-review skill.
Baseado na classificação ocupacional SOC
| name | aws-cli |
| description | Use the correct AWS CLI profile when running AWS commands based on the target environment. |
When running AWS CLI commands, always pass the --profile flag based on the target environment.
Update the profile map below with your AWS profile names as configured in ~/.aws/config:
| Environment | Profile |
|---|---|
| Production | <your-prod-profile> |
| Staging / Non-Prod | <your-nonprod-profile> |
aws <service> <command> --profile <profile> [options]
# Production
aws s3 ls --profile my-prod-profile
# Staging / Non-Prod
aws s3 ls --profile my-nonprod-profile
--profile explicitly — never rely on the default profile.