What problem does it solve?
Figuring out why CI is red on a PostHog pull request or on master requires digging through GitHub Actions logs, merge-queue branches, and flaky-test history by hand. This Skill triages failing runs, classifies the failure, and reports the smallest actionable finding without rerunning CI or posting to GitHub.
Core Features & Use Cases
- CI insights digest: Starts from
hogli ci:insights to see cross-run failure history and classify failures as breaking master, blocking the merge queue, flaky, or PR-only.
- Failure classification: Maps log signals to classes such as code regression, flaky test, lint, typecheck, snapshot diff, migration, codegen drift, and infra/runner issues.
- Safe read-only inspection: Uses
gh and engineering-analytics MCP tools for log analysis while forbidding reruns, comments, pushes, or workflow edits without approval.
- Use Case: A developer asks why their PR was kicked from the merge queue; the Skill locates the failing trunk-merge run, extracts the failing job and step, classifies it, and suggests the narrowest local reproduction command.
Quick Start
Ask the assistant to investigate why CI is failing on your current PostHog pull request and classify the failure.