メニュー
Multi-cluster reference data for troubleshooting across EMEA, APAC, NAM. Contains kubectl contexts, ArgoCD cluster names, and Log Analytics workspace details per region. Auto-loaded by the troubleshooter agent.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | clusters |
| description | Multi-cluster reference data for troubleshooting across EMEA, APAC, NAM. Contains kubectl contexts, ArgoCD cluster names, and Log Analytics workspace details per region. Auto-loaded by the troubleshooter agent. |
| disable-model-invocation | true |
Edit the values below to match your environment.
| Region | kubectl Context | ArgoCD Cluster Name | Azure Resource Group |
|---|---|---|---|
| EMEA | aks-emea-prod | emea-production | rg-emea-prod |
| APAC | aks-apac-prod | apac-production | rg-apac-prod |
| NAM | aks-nam-prod | nam-production | rg-nam-prod |
Single instance manages all 3 clusters. App naming: <service>-<region>.
Each app's destination.server identifies the target cluster.
kubectl --context=aks-emea-prod get pods -n <namespace>
kubectl --context=aks-apac-prod logs deployment/<app> --tail=200
kubectl --context=aks-nam-prod get events -n <namespace>
Resolve the workspace GUID first, then query:
# Get workspace GUID (cache for session)
WORKSPACE=$(az monitor log-analytics workspace show \
--resource-group rg-<region>-<workload>-prod \
--workspace-name law-<region>-<workload>-prod \
--query customerId -o tsv)
# Query using the GUID
az monitor log-analytics query \
--workspace "$WORKSPACE" \
--analytics-query "<KQL>" \
--output json
See the app-insights skill for table/field name mappings (e.g.
AppEvents instead of customEvents, Properties instead of
customDimensions).
for region in emea apac nam; do
echo "=== $region ==="
kubectl --context="aks-${region}-prod" get pods -n <ns> -l app=<svc>
done
WORKSPACE=$(az monitor log-analytics workspace show \
--resource-group rg-<region>-<workload>-prod \
--workspace-name law-<region>-<workload>-prod \
--query customerId -o tsv) && \
az monitor log-analytics query \
--workspace "$WORKSPACE" \
--analytics-query "AppExceptions | where TimeGenerated > ago(2h) | summarize count() by ExceptionType" \
--output json
Feature development pipeline for GitHub repositories using Claude LLMs. Requirements engineer takes input from specs.md or user, creates a GitHub issue as feature request, then architect plans, tdd-developer implements, qa tests, and reviewer peer-reviews the pull request. Triggers on: github pipeline, github feature, claude pipeline, specs pipeline.
Full feature development pipeline for GitLab repositories using Copilot CLI agents and Jira integration. Takes a Jira item through requirements engineering, test planning, architecture, TDD development, testing, and MR review. Triggers on: gitlab pipeline, gitlab feature, copilot pipeline.
Incident response pipeline for GitLab repositories using Copilot CLI, Jira, and troubleshooter. Takes a Jira incident, investigates root cause, optionally fixes via TDD, and reviews the merge request. User decides whether to fix or just document findings on the Jira ticket. Triggers on: gitlab incident, incident pipeline, troubleshoot gitlab.
Entry point for all new work. Orchestrates the full agent pipeline: architect (Opus) designs spec+todo, tdd-developer (Sonnet) implements via TDD, qa (Opus) hunts spec/impl gaps, reviewer (Sonnet) reviews code. Triggers on: plan, new feature, start work, build feature.
Create an Architecture Decision Record in docs/decisions/ and optionally sync to Confluence for business projects. Use when making significant technical decisions. Triggers on: architecture decision, ADR, technical decision.
Ultra-compressed communication mode — cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Slash-only: /caveman to enable, "stop caveman" / "normal mode" to disable.