debugging-ci-failures
系统化定位失败根因并指导可复现最小案例，适合稳定运维流程。
诊断可能需要访问私有 CI 信息或触发可见操作，注意权限与可见性。
诊断 PostHog 仓库中 GitHub Actions CI 失败原因并定位首要问题。
定位并解释 PostHog 仓库里失败的 GitHub Actions CI，找出首要失败点并给出重现或修复建议。CI 报红、某个 workflow/job 或测试失败时就用它。流程会先看 hogli ci:insights 作为总体信息源，然后分类失败类型、尝试最小化本地复现，并避免在公共跑道上随意重跑造成更多噪音。
▸ 展开 SKILL.md 英文原文
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (aggregated cross-run CI intelligence), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub.
帮我安装这个 skill：https://raw.githubusercontent.com/PostHog/posthog/master/.agents/skills/debugging-ci-failures/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/PostHog/posthog/master/.agents/skills/debugging-ci-failures/SKILL.md"# Debugging PostHog CI failures Find the first meaningful failure, classify it, reproduce the smallest useful case locally when appropriate, and report the result. Avoid public-visible or irreversible actions unless the user explicitly asks. Always start with the `hogli ci:insights` digest. It is the institutional, cross-run source of truth, and it is fresher and more reliable than scraping `gh run list` / the GitHub Actions API, which can lag or rate-limit. This skill triages and classifies. Once a failure is confirmed flaky, hand off to the `fixing-flaky-tests` skill, which owns local reproduction, root-cause fixing, and N-run validation. ## Safety rules Do not do any of these without