investigating-ci-failures
investigating-ci-failures is a Build, CI & test failure triage skill for AI agents, published by PostHog in the posthog repository on GitHub. Skillspace rates investigating-ci-failures D (64/100) and it passed the safety scan; the rating is based on static analysis only.
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this failure start". Works from the engineering_analytics warehouse views (engineering_analytics_ci_failures, engineering_analytics_ci_job_history) plus the CI failure logs. Not for aggregate CI health, cost, or merge bottlenecks (use diagnosing-ci-and-merge-bottlenecks) and not for building saved insights (use turning-engineering-analytics-into-insights).
- Grade
- D
- Quality
- 64 / 100
- Safety
- Passed
- GitHub stars
- 35,560
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 82 / 100
- Maturity
- Structured: ships references or scripts
- Security scan
- No issues found
- License
- Not declared. Check the repository before reusing it.
- Adoption
- Adopted by 1 other repositories, in 0 collections
- Scope
- Repo-internal: written for the repository it lives in. Queries PostHog's own engineering_analytics warehouse views about their CI
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.