whats-on-fire

This skill should be used when the user asks "what's on fire", "what's on fire today", "what's broken", "what's broken across our products", "what's stuck", "what's red", "anything burning", "portfolio status", "portfolio health", "how's the portfolio looking", "which product needs attention", "cross-product status", "any leaked secrets", "security exposure", or wants one cross-product sweep of production failures and stalled work spanning EVERY repo in a GitHub org rather than a single repository. Pulls Sentry issues and cron monitors, org-wide open issues and pull requests, failing workflows, Dependabot exposure, and structural blind spots (products with no error monitoring, no alerting, or no dependency scanning), then ranks them across products and routes each one to the owning repo. Read-only — never files issues, never mutates state. For deep single-repo prioritization, defer to that repository's own survey-work skill.