What problem does it solve? GitHub bills two unrelated meters — Actions minutes and GHAS seats — and teams routinely optimize the wrong one, chase billing anomalies with workflow edits, or pay for runaway matrices and poor caches. This Skill traces spend from product to repository, workflow, and run so fixes target the actual cost driver. ## Core Features & Use Cases - Spend breakdown: Runs scripts that rank billing by product, SKU, and repository using the enhanced-billing usage API, plus GHAS committer-seat consumption for Secret Protection and Code Security. - Per-repo drill-down: Classifies a repo's driver as high run volume, matrix fan-out, long runs, or a billing anomaly, with per-job rounding and OS multiplier analysis (Linux 1x, Windows 2x, macOS 10x). - Ranked fixes shipped via PR: Applies levers like concurrency cancel-in-progress, path filters, cron reduction, cache warming, and seat right-sizing through branch-and-PR workflows, and drafts GitHub Support tickets for genuine mis-billing. - Use Case: An organization sees a surprise GitHub bill; the Skill identifies that one private repo's test matrix accounts for 90% of Actions minutes, then ships a PR that shards jobs and shares build caches. ## Quick Start Ask the assistant to diagnose why your GitHub Actions bill is high for your enterprise or organization and propose cost-reduction fixes.
