What problem does it solve? Azure teams often lack per-resource-group budgets, making it impossible to know whether current spending is on track until the invoice arrives. This Skill analyzes actual historical spend, calculates data-driven budgets, and stores them alongside cost anomaly data in a GitLab knowledge base. ## Core Features & Use Cases - Budget Generation: Fetches 3 months of Azure Cost Management data per resource group, computes the median monthly spend, and writes a _budget.json with a 20% buffer to each RG folder in the cost-anomalies KB. - Burn Rate Status: Compares current month-to-date spend against stored budgets and classifies each RG as On track, Elevated, WARN, or ALERT with projected month-end totals. - Manual Overrides & Gap Filling: Set a specific budget for any RG manually, or run --fill-gaps to generate budgets only for RG folders missing one. - Use Case: After noticing a spike in a production resource group, run the status command to see that legacy-r6 is burning at 1.49x its budget and projected to exceed it by $5,400, then escalate before month-end. ## Quick Start Ask the assistant to generate Azure resource group budgets from recent spend, for example: "Generate budgets for all subscriptions in the cost-anomalies KB."
