aro-env-info
01Skill Claude CodeCodex
Discover infrastructure endpoints (like kusto and grafana) for ARO Classic, ARO HCP and related infrastructure available to currently logged-in Azure user.
Skill Claude CodeCodex
Discover infrastructure endpoints (like kusto and grafana) for ARO Classic, ARO HCP and related infrastructure available to currently logged-in Azure user.
Skill Claude CodeCodex
Explore datasources and run PromQL queries against ARO HCP Grafana instances — discover datasource UIDs and available metrics, then query resource utilization, request latency, error rates, cluster health, tenant utilization, and more. (Use aro-env-info first).
Skill Claude CodeCodex
Explore and query ARO Kusto clusters — list databases, tables, and schemas, then run KQL queries to search logs, investigate errors, and debug provisioning, cluster lifecycle, and operational data. (Use aro-env-info first).
Skill Claude CodeCodex
Query CIHealth REST API to retrieve CI failure history, failure patterns, and run data for ARO-HCP. Use when investigating CI failures, triaging provision or e2e issues, or reviewing failure trends.
Skill Claude CodeCodex
Calculate and explain ARO-HCP E2E capacity from the checked-in Bicep role assignments, e2e-slots.yaml, and docs/ci scaling constraints. Use for per-run role-assignment cost, test concurrency, slot sizing, subscription headroom, and maximum concurrent E2E job questions.
Skill Claude CodeCodex
List ARO HCP EV2 rollouts (releases) for a specific environment (test, stg, prod, int). Use when asked things like "get all ev2 releases for prod", "show EV2 rollouts for stage", or "what EV2 rollouts are running in test".
Skill Claude CodeCodex
Triage and analyze e2e-parallel provision failures in DEV. Covers Bicep/ARM deployments, Helm releases, Shell steps, and CI or platform infrastructure. Use when investigating why e2e-parallel provision failed.
Skill Claude CodeCodex
List ARO HCP pipeline releases (Azure DevOps builds) for a specific environment (test, stg, prod, int). Use when asked things like "get all releases for test", "show stage releases", or "what's releasing to prod".
Skill Claude CodeCodex
Investigate Azure Resource Manager operations in internal ARM Kusto logs. Use for correlation-ID timelines, downstream resource-provider calls, long-running operations, deployment failures, retries, and escalation evidence.
Skill Claude CodeCodex
Verify locally that an ARO-HCP change will survive EV2 manifest generation in sdp-pipelines — catching the resolve/dunder-placeholder failures (e.g. range over an array config) that ARO-HCP's own CI cannot see.
Skill Claude CodeCodex
Create a well-formed JIRA issue in the AROSLSRE project with correct fields, labels, components, sprint assignment, and JIT documentation when applicable. For oncall investigations, creates a structured Story with sub-tasks for investigation, mitigation, and follow-up. Follows ARO HCP JIRA governance conventions.
Skill Claude CodeCodex
Groom the JIRA backlog for the ARO HCP space. Detect stale tickets, enforce close policies, run backlog refinement checks, prepare tickets for weekly status updates, and flag stuck work as Blocked. Use when grooming the backlog, reviewing stale issues, preparing for program calls, or enforcing JIRA hygiene.
Skill Claude CodeCodex
Manage JIRA issue lifecycle and status transitions in the ARO HCP space. Covers workflow states, transition rules, Blocked handling, Release Pending, and full lifecycle for all issue types including Features, Initiatives, Epics, Tasks, Bugs, and Spikes.
Skill Claude CodeCodex
Manage an oncall shift end-to-end — accept handover, prioritize tasks, track work in a local shift log, and generate structured handover notes for the next shift. Use whenever a user starts an oncall shift, receives handover notes, wants to update shift status, or needs to create handover notes.
Skill Claude CodeCodex
Guide and track ARO HCP release rollouts through INT, Stage, and Prod environments. Use when performing, monitoring, retrying, or troubleshooting an EV2 rollout.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: