git:20260708.e42b71f to git:20260911.3a0a7c8

1 added, 1 removed. Audit A to A.

---
name: "cicd-infra-discover"
description: "Generate cloud resource discovery script for IaC import"
---
<!-- GENERATED by claude-power-pack - scripts/codex-skill-sync.py; edit .claude/commands/cicd/infra-discover.md instead -->
# /cicd-infra-discover - Cloud Resource Discovery
Generate a discovery script that audits existing cloud resources and outputs them in a format suitable for IaC import (`terraform import`, etc.).
## Instructions
1. **Detect cloud provider** from `.claude/cicd.yml` or ask the user (aws/azure/gcp).
2. **Generate the discovery script:**
```bash
- PYTHONPATH="$CPP_DIR/lib:$PYTHONPATH" python3 -m lib.cicd infra-discover --path "$(pwd)" --cloud aws --write
+ PYTHONPATH="$CPP_DIR:$PYTHONPATH" uv run --project "$CPP_DIR" python -m lib.cicd infra-discover --path "$(pwd)" --cloud aws --write
```
3. **Optionally run the script** if the user has CLI tools configured:
```bash
bash infra/scripts/discover-aws.sh
```
4. **Report findings** and suggest which resources to import first (most critical/fragile).
## When to Use
- Starting IaC from scratch ("no documentation exists yet")
- Auditing what exists before codifying it
- Building a manifest for `terraform import`
## Key Principle
Even if you only plan to run infrastructure changes once, codify them. The value is having an executable runbook, not a stale wiki page.
## Related
- `/cicd-infra-init` - Scaffold IaC directory structure
- `/cicd-infra-pipeline` - Generate CI/CD pipelines with approval gates