How do I install the CI Triage skill?

Run npx skillmds@latest add earayu/ci-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI Triage?

earayu (@earayu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI Triage by earayu — Agent Skill

Name: CI Triage
Author: earayu

File contents

CI Failure Triage

Use this skill whenever a PR's CI goes red.

1. Get the signal, not the whole log

Never dump a full failed-run log into context (10-50KB+). Use the wrapper's key-line extraction (github.ci.failed_log_signal_patterns, capped by failed_log_max_lines). Pull the raw log only when a human explicitly asks.

2. Classify the failure

Symptom	Class	Action
`psycopg2 ... Connection refused` / `port 5432` / "Apply migrations"	runner infra (postgres OOM/contention)	Do NOT loop-retry. Escalate / wait off-peak / evidence-based admin override.
kube-apiserver readiness 500 / kube-proxy CrashLoop / node not-ready	runner infra (kind cluster)	Same.
`test_openapi_route_coverage_matrix... AssertionError: N == M`	matrix drift	`git merge origin/<default>` into branch (brings updated matrix). Proven fix.
`Type error` / `tsc` / `Would reformat` / ruff	real code	Fix precisely. Don't retry.
compose/kind smoke ✅ but lint-and-unit ❌ on an FE-only PR	code clean → infra	Treat the red as infra; pursue the infra path.

3. Don't double-trigger

If a monitor/PM script or another agent is already auto-rerunning, do NOT also push an empty commit or gh run rerun. Coordinate so exactly one owner pulls the trigger. Empty-commit retrigger re-runs ALL checks → waste + runner contention.

4. Persistent failure = escalate, not loop

≥3 failures of the same check across reruns is NOT a transient flake. Pull the real log, name the root cause, escalate (SRE / off-peak retry / evidence-based admin override) instead of an infinite loop.

5. i18n / contract sync gotcha

When you i18n a user-facing string (raw → t('...')), grep contract/snapshot tests for the raw string before merging — they may assert on it and turn main red after merge.

---name: ci-triagedescription: Decision tree for a red CI run. Use BEFORE retrying — blind re-runs burn the shared GitHub rate limit and hide real bugs.---# CI Failure TriageUse this skill whenever a PR's CI goes red.## 1. Get the signal, not the whole logNever dump a full failed-run log into context (10-50KB+). Use thewrapper's key-line extraction (`github.ci.failed_log_signal_patterns`,capped by `failed_log_max_lines`). Pull the raw log only when a humanexplicitly asks.## 2. Classify the failure| Symptom | Class | Action ||---|---|---|| `psycopg2 ... Connection refused` / `port 5432` / "Apply migrations" | runner infra (postgres OOM/contention) | Do NOT loop-retry. Escalate / wait off-peak / evidence-based admin override. || kube-apiserver readiness 500 / kube-proxy CrashLoop / node not-ready | runner infra (kind cluster) | Same. || `test_openapi_route_coverage_matrix... AssertionError: N == M` | matrix drift | `git merge origin/<default>` into branch (brings updated matrix). Proven fix. || `Type error` / `tsc` / `Would reformat` / ruff | real code | Fix precisely. Don't retry. || compose/kind smoke ✅ but lint-and-unit ❌ on an FE-only PR | code clean → infra | Treat the red as infra; pursue the infra path. |## 3. Don't double-triggerIf a monitor/PM script or another agent is already auto-rerunning, doNOT also push an empty commit or `gh run rerun`. Coordinate so exactlyone owner pulls the trigger. Empty-commit retrigger re-runs ALL checks→ waste + runner contention.## 4. Persistent failure = escalate, not loop≥3 failures of the same check across reruns is NOT a transient flake.Pull the real log, name the root cause, escalate (SRE / off-peakretry / evidence-based admin override) instead of an infinite loop.## 5. i18n / contract sync gotchaWhen you i18n a user-facing string (raw → `t('...')`), grepcontract/snapshot tests for the raw string before merging — they mayassert on it and turn main red after merge.

Frequently asked questions

CI Triage