Skip to content

mmaideveloper/aiarchitecttoolkit / skills/azure-review

azure-review

Verified

Review an Azure solution architecture or implementation for platform fit, reliability, security, cost, operations, performance, governance, and deployment evidence. Use for Azure design reviews and Azure readiness assessments; do not use for deployment or generic cloud reviews without Azure scope.

FileKindSize
SKILL.mdskill md2.9 KB
agents/openai.yamlconfig222 B
references/azure-review-method.mdmarkdown1.3 KB

references/azure-review-method.md

View on GitHub
# Azure Review Method

Use a workload-specific matrix:

| Area | Requirement or target | Azure design/configuration | Evidence | Result | Finding/action |
|---|---|---|---|---|---|
| <area> | <SLO, RTO/RPO, policy, constraint> | <service and pattern> | <ADR, IaC, policy, test, telemetry, official guidance> | Meets / Partially meets / Does not meet / Not verified / Not applicable | <action> |

Review the current Azure Well-Architected pillars—reliability, security, cost optimization, operational excellence, and performance efficiency—plus governance, sustainability, and migration/exit constraints when relevant. Weight them using documented business and quality-attribute priorities rather than averaging scores blindly.

Severity:

- `Critical`: credible severe security, compliance, data-loss, or broad outage risk; stop release.
- `High`: required SLO, recovery target, policy, or accepted architecture decision is unlikely to be met.
- `Medium`: material operability, cost, scaling, resilience, or governance weakness.
- `Low`: localized optimization or maintainability issue.

Record the authoritative URL and access date for time-sensitive Azure facts. When evidence conflicts, prefer observable current configuration for deployed-state claims and authoritative approved artifacts for intended-state claims; report the drift explicitly.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall