القائمة
Plan infrastructure changes — Terraform modules, Helm charts, CI/CD pipelines. Use when the user wants to add or modify cloud infrastructure, Kubernetes resources, or deployment pipelines.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Verify hexagonal architecture layer rules, Result pattern usage, and coding conventions. Use as a quick local check during development — fast and focused on architecture rules only. For full security + quality review, use /code-review instead.
Review code changes for security, architecture, and quality issues. Use for deep PR-level review — checks OWASP vulnerabilities, hexagonal architecture violations, code smells, and test gaps. For a quick architecture-only check, use /check-architecture instead.
Complete current task with all quality gates, code review, QA check, and submit PR. Use when implementation is done and you want to run the full verification pipeline (build, lint, tests, review, QA) and create the pull request.
Complete infrastructure task — lint, validate, review, and submit PR. Use when an infrastructure-only branch is ready for submission — runs Terraform/Helm validation and creates the PR, skipping .NET/frontend checks.
Scaffold a new frontend feature module with page, components, API service, and hooks. Use whenever the user wants to add a new page, dashboard section, UI module, or frontend feature to the React app.
Capture a screenshot of a URL or route with one command. Use whenever the user wants to take a screenshot, capture a page, see what a route looks like, or visually verify a page. Supports mobile viewport with --mobile and unauthenticated mode with --no-auth.
| name | infra-plan |
| description | Plan infrastructure changes — Terraform modules, Helm charts, CI/CD pipelines. Use when the user wants to add or modify cloud infrastructure, Kubernetes resources, or deployment pipelines. |
| allowed-tools | Read, Glob, Grep, Task |
| user-invocable | true |
Break down an infrastructure change into implementation tasks. This is the infra equivalent of /plan-feature.
{description} — What infrastructure change is needed (required)Understand the request — Parse what the user wants to change (new module, modify existing, add chart, change CI/CD)
Analyze current state — Read relevant files:
infra/terraform/modules/ — existing Terraform modulesinfra/terragrunt/ — environment configurations and dependenciesdeploy/charts/ — existing Helm charts.github/workflows/ — CI/CD pipelinesIdentify scope — Categorize the change:
Map dependencies — Terraform modules have ordering constraints via Terragrunt dependencies. Identify:
Create plan — Output a structured plan:
## Infrastructure Change Plan
### Summary
{one-line description}
### Category
Terraform | Helm | CI/CD | Cross-cutting
### Changes Required
#### {Category 1}
1. {task} — {file or directory affected}
2. {task} — {file or directory affected}
#### {Category 2} (if cross-cutting)
1. {task} — {file or directory affected}
### Dependency Order
{execution order considering Terragrunt dependencies}
### Validation Steps
- [ ] `terraform validate` passes for affected modules
- [ ] `terraform fmt -check` passes
- [ ] `terragrunt validate` passes
- [ ] `helm lint` passes (if charts changed)
- [ ] `helm template` renders without errors (if charts changed)
### Risk Assessment
- Blast radius: {low/medium/high}
- Reversibility: {easy/hard}
- Requires `terraform plan` review: {yes/no}