automation-audit-ops

Automation audit is the process of inventorying live automation surfaces to classify hooks, GitHub Actions, and MCP servers as configured, stale, broken, or missing. You need it when troubleshooting broken automations or consolidating redundant CI paths before making changes.

To check if GitHub Actions workflows and webhooks are broken or stale, audit your live automation surface using concrete proof paths like workflow runs and hook logs. This classifies each automation as recently verified, stale, broken, or missing without assuming tools work from config alone.

Yes, this automation audit approach works with MCP servers and local runtime hooks by producing a real-time surface map grouped by where they run. It requires concrete evidence like file paths and exact failure signatures to classify connectors and wrappers across connected external systems.

To consolidate overlapping automation paths across repo CI and connected systems, audit the live surface to identify redundant jobs and hooks. The audit outputs keep, merge, cut, and fix-next recommendations backed by proof paths to collapse overlap into one canonical lane.

The best way to troubleshoot an automation isn't working escalation is to audit the live automation surface before fixing anything. This generates an evidence-first inventory classifying which jobs, hooks, and connectors are authenticated, broken, or missing to prevent rewriting the wrong things.

You should use concrete proof paths instead of config files when auditing automations because tools may appear configured but actually be stale or broken. Proof paths like hook logs and exact failure signatures ensure evidence-backed classification for accurate keep, merge, cut, or fix-next decisions.