---
name: cloud-change
description: Make a bounded cloud CLI change using an explicit account, region and evidence-based approval boundary.
---

1. Read repository instructions and identify the intended provider, account/project/subscription and region.
2. Confirm identity with a non-secret command; never display access keys, tokens or secret values.
3. Inspect the current resource and quotas before proposing a change.
4. Prefer infrastructure-as-code over an unrecorded console or CLI mutation when the repository supports it.
5. Show the exact target, cost/security implications and rollback approach, then wait for approval for shared or production changes.
6. Execute with least privilege and verify resource state, logs and tags/labels.
7. Record commands and durable configuration changes without recording credentials.