메뉴
Use when the user asks to update, deploy, or apply changes to all Pulumi stacks (core and all stacks in the stacks/ folder). Trigger on phrases like "update all stacks", "deploy all stacks", "pulumi up all", or "apply all stacks".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when creating or editing TypeScript code in the orange-lab repo — stacks, components (`stacks/<module>/components/`, `components/`), or the `@orangelab/pulumi` library (`packages/pulumi/src/`). Covers code style, component patterns, Pulumi config conventions, and secrets handling. Not needed for markdown/documentation-only changes.
Use when the user asks to create, update, or revise documentation for an application component — typically a `<app>.md` file under `stacks/<module>/components/<app>/`. Trigger on phrases like "document `<app>`", "write `<app>`.md", "update `<app>` docs", "add docs for `<app>`", "backfill `<app>` links". The components folder is a Pulumi convention; users think of these as applications, so the skill is named accordingly.
Use when the user asks to create, update, or revise documentation for a stack module — typically the `README.md` at `stacks/<module>/README.md`. Trigger on phrases like "document `<module>` stack", "update `<module>` README", "write stack README", "add module docs". Distinct from `document-app` (per-component docs); a module README is the entry point that lists and links its components.
Use ONLY when the user asks to create a new release, draft release, or release notes for the orange-lab project. Trigger on phrases like "create release", "draft release notes", or "release 0.6.0".
SOC 직업 분류 기준
| name | update-stacks |
| description | Use when the user asks to update, deploy, or apply changes to all Pulumi stacks (core and all stacks in the stacks/ folder). Trigger on phrases like "update all stacks", "deploy all stacks", "pulumi up all", or "apply all stacks". |
Updates the core stack and all child stacks in the stacks/ folder.
Compile shared packages first:
npm run build
Pulumi.<stack>.yaml in the project root. Use that stack name.stacks/, look for Pulumi.<stack>.yaml. Collect all stack names. Each child stack must be run from its own directory (stacks/<name>/), not the project root.Run previews in parallel where safe:
stacks/<name>/ directoryCore stack:
pulumi preview --json -s <stack-name>
Child stacks (run from stacks/<name>/):
pulumi preview --json -s <stack-name>
If a stack has no changes, note that. Otherwise, extract from JSON:
create, update, delete, replace countsPresent a table:
| Stack | Create | Update | Delete | Replace | Status |
|---|---|---|---|---|---|
| lab (core) | 2 | 5 | 0 | 1 | changes |
| lab-apps | 0 | 0 | 0 | 0 | no changes |
| lab-ai | 1 | 3 | 0 | 0 | changes |
Then ask: "Apply all stacks?" (yes/no). Do not proceed without explicit confirmation.
Only if core has changes from preview. Run from project root:
pulumi up --yes -s <core-stack-name>
Wait for completion. If this fails, stop and report the error. Do not update child stacks.
Only run on child stacks that have changes from preview. Run them simultaneously from their respective stacks/<name>/ directories:
pulumi up --yes -s <child-stack-name>
Present a final summary:
| Stack | Result | Notes |
|---|---|---|
| lab (core) | ✅ success | |
| lab-apps | ✅ success | no changes |
| lab-ai | ❌ failed | error message |
For failures, include the last few lines of the error output so the user can diagnose.