automation-audit-ops

Auditing live CI workflows and hooks requires an evidence-first inventory that maps local runtime automation, repo CI, and external integrations, classifying each item as active, broken, or redundant with proof paths. This yields keep, merge, cut, or fix-next recommendations for safe cleanup.

Finding broken or redundant automation jobs involves state classification across connected environments, separating configured, authenticated, recently verified, and stale items. Overlap analysis then identifies duplicate capability and missing items, providing evidence-backed guidance for consolidation.

Inventorying lifecycle hooks and external integrations builds a proof-backed map of notification surfaces and connected runtime automation. It classifies configured, authenticated, and stale connectors, identifying overlaps and breakage to guide merge or cut decisions.

An automation audit can identify missing capability by analyzing configured, authenticated, and recently verified items across repo CI workflows and external integrations. It detects gaps and overlaps, then provides evidence-backed fix-next recommendations to restore missing capability.

An automation audit works with local runtime automation and scheduled jobs by applying evidence-first inventory and state classification. It requires connected environments with repo CI, external integrations, and lifecycle hooks to classify active, broken, and redundant items with proof paths.