Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed.
Install Investigating CI Failures
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog investigating-ci-failures --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .claude/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .claude/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failuresType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog investigating-ci-failures --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .agents/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .agents/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog investigating-ci-failures --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .cursor/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .cursor/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/engineering_analytics/skills/investigating-ci-failures--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog investigating-ci-failures --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .gemini/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .gemini/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog investigating-ci-failuresInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .github/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .github/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill investigating-ci-failures -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog investigating-ci-failures --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/engineering_analytics/skills/investigating-ci-failures .opencode/skills/investigating-ci-failures && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "investigating-ci-failures" agent skill from https://github.com/PostHog/posthog/tree/master/products/engineering_analytics/skills/investigating-ci-failures into .opencode/skills/investigating-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-ci-failures", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
investigating-ci-failures- GitHub stars
- 40k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,417 words
- Files
- 2 (incl. references)
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed.
- Who broke master
- SKILL.md covers Start wide: what's broken…, The four failure shapes, Trunk break → culprit and Flaky → corroborate, don't guess, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Why did this test fail in CI
What it does
Investigating CI Failures is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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 engineeringanalytics warehouse views (engineeringanalyticscifailures, engineeringanalyticscijobhistory) plus the CI failure logs. Not for aggregate CI health, cost, or merge bottlenecks (use…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/investigation-queries.md`).
It sits in Testing & QA, covering Failing and flaky tests. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- Who broke master
- Why did this test fail in CI
- Is this failure my PRs fault
- Is this test flaky
Example prompts
- “s fixed. Use for”
- “why did this test fail in CI”
- “is this failure my PR”
- “/investigating-ci-failures”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit c012c8d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Investigating CI Failures loads about 2.9k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 164 tokens; SKILL.md has 1,417 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,417 words (~2,851 tokens).
“The job: take one failing test or one red run and get to a verdict a developer can act on — yours / trunk-borne / flaky, and when trunk-borne: the culprit SHA, its author, the PR, and whether a fix…”
- name
- investigating-ci-failures
Files
SKILL.md and 1 other file (references) in products/engineering_analytics/skills/investigating-ci-failures of PostHog/posthog.
- SKILL.md
- references/investigation-queries.md
Open the folder on GitHubat commit c012c8d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Investigating CI Failures next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Investigating CI Failures this skillPostHog/posthog | 40k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Triage CI FailureDataDog/datadog-agent | 3.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Fix Ready PRsfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Trx Analysismicrosoft/vstest | 969 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Triage CI Failure
DataDog/datadog-agent
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Fix Ready PRs
fastrepl/anarlog
Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.
- Official
Trx Analysis
microsoft/vstest
Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
More from PostHog/posthog
All 254 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Categories
Questions about Investigating CI Failures
What does Investigating CI Failures do?
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Investigating CI Failures is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed.
When should I use Investigating CI Failures?
Investigating CI Failures fits situations like: who broke master; why did this test fail in CI; is this failure my PRs fault; is this test flaky.
How do I install Investigating CI Failures in Claude Code?
Run `npx skills add PostHog/posthog --skill investigating-ci-failures -a claude-code`. Or copy the skill folder (products/engineering_analytics/skills/investigating-ci-failures in PostHog/posthog) into .claude/skills/investigating-ci-failures in your project. Claude Code loads it when a task matches its description.
How do I install Investigating CI Failures in Codex?
Run `npx skills add PostHog/posthog --skill investigating-ci-failures -a codex`. Or copy the skill folder (products/engineering_analytics/skills/investigating-ci-failures in PostHog/posthog) into .agents/skills/investigating-ci-failures in your project. Codex loads it when a task matches its description.
Can I use Investigating CI Failures in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill investigating-ci-failures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-ci-failures, .gemini/skills/investigating-ci-failures, .github/skills/investigating-ci-failures and .opencode/skills/investigating-ci-failures in your project.
What does Investigating CI Failures need to run?
SKILL.md names no scripts, command-line tools or credentials: Investigating CI Failures is instructions for the agent only. Our summary lists: Docker.
Does Investigating CI Failures access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Investigating CI Failures safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Investigating CI Failures use?
Investigating CI Failures has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Investigating CI Failures use?
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Investigating CI Failures?
Skills that share tags, products or a category with Investigating CI Failures: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating CI Failures?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.