メニュー
Azure DevOps pull request workflows and pipeline design standards. Use when creating or reviewing ADO pull requests, writing azure-pipelines.yml, designing build/release pipelines, or setting branch policies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Shape answers so they are immediately actionable instead of long. Use on any response that would otherwise run long — multi-step tasks, explanations, plans, reviews with many findings, or answers that hand back commands, paths, or snippets to run. Leads with the next action, numbers steps, restates progress, caps lists, and gives concrete time estimates. Complements caveman (which handles tone); this handles shape.
Senior software architect for system design, ADRs, microservices evaluation, technology trade-off analysis. Use when designing system architecture, evaluating patterns, creating ADRs, analyzing technology choices, or planning migrations.
Go CLI development with Cobra command hierarchy, Bubbletea interactive TUI, Lipgloss terminal styling, Charmbracelet ecosystem (Bubbles, Huh forms, Glamour markdown rendering), and shell completions. Use when building CLI tools, adding subcommands, creating interactive TUI, styling terminal output, or implementing shell completions.
Cloud architecture design, migration, optimization, and disaster recovery across AWS and Azure. Use when designing VPCs/VNets, IAM/RBAC, compute/storage architectures, cost optimization, multi-cloud patterns, or planning migrations. Both Terraform and CLI approaches.
Datadog monitoring strategy, alert design, tagging governance, dashboard patterns, SLO strategy, log management, cost optimization, and cross-pillar correlation workflows. Use when making architectural decisions about what to monitor, how to alert, how to tag, or how to structure Datadog for a service or platform. Delegates execution to pup CLI and infrastructure-as-code to sre-engineer.
Kubernetes workload management, Helm chart development, cluster troubleshooting, custom operators, configuration management, and multi-cluster administration. Use when deploying workloads, writing Helm charts, debugging pods, creating operators, managing ConfigMaps/Secrets/RBAC, or working with multi-cluster setups.
| name | Azure DevOps Standards |
| description | Azure DevOps pull request workflows and pipeline design standards. Use when creating or reviewing ADO pull requests, writing azure-pipelines.yml, designing build/release pipelines, or setting branch policies. |
| version | 1.0.0 |
| tags | ["azure-devops","ado","pull-requests","pipelines","ci-cd","yaml"] |
azure-pipelines.ymlazure-pipelines.yml lives in the repo, not ADO UIscript: steps reduce supply chain riskaz repos pr create nor az repos pr update auto-applies it (see PR
reference for locations and the CLI workflow)Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Pull Requests | references/pull-request-conventions.md | Creating a PR (always — for the template workflow), branch strategy, PR requirements, branch policies, code review |
| Pipelines | references/pipeline-design.md | Pipeline YAML structure, templates, security, naming |
| Artifacts & Promotion | references/artifacts-and-promotion.md | Artifact management, environment promotion flow |
PR Build (validate + plan) -> main Build (plan) -> Dev (auto-apply) -> Staging (approval) -> Production (approval)
trigger: '*' — always scope triggers to specific branches/pathsCache@2 task for .terraform/)script: step would doterraform apply without a saved plan fileaz repos pr create/update do not)