Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

ci-triage

by WJDdidi-1version 0.1.2i★ 0iRuns on your computerRepository ↗
Registry nameio.github.WJDdidi-1/ci-triage

How to install

What it does

Group failed GitHub Actions runs by root cause; separate real regressions from flaky failures.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install ci-triage. Follow https://mcp.popnx.com/i/wjddidi-1-ci-triage.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 16, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server ci-triage for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "ci-triage": { "command": "npx", "args": [ "-y", "ci-triage-cli" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ci-triage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "ci-triage": {
          "command": "npx",
          "args": [
            "-y",
            "ci-triage-cli"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use ci-triage and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using ci-triage or shows a ci-triage tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect ci-triage yet

ci-triage runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect ci-triage

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server ci-triage for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user ci-triage -- npx -y ci-triage-cli 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ci-triage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user ci-triage -- npx -y ci-triage-cli
  4. Type /mcp in Claude Code

    You should see ci-triage listed as connected

  5. Try it

    Use ci-triage and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using ci-triage or shows a ci-triage tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server ci-triage for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "ci-triage": { "command": "npx", "args": [ "-y", "ci-triage-cli" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ci-triage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use ci-triage and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using ci-triage or shows a ci-triage tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server ci-triage for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "ci-triage": { "type": "stdio", "command": "npx", "args": [ "-y", "ci-triage-cli" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the ci-triage tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use ci-triage and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using ci-triage or shows a ci-triage tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use ci-triage💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user ci-triage -- npx -y ci-triage-cli

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "ci-triage": {
      "command": "npx",
      "args": [
        "-y",
        "ci-triage-cli"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "ci-triage": {
      "command": "npx",
      "args": [
        "-y",
        "ci-triage-cli"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "ci-triage": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ci-triage-cli"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.1.2
Published to registryi
Nov 16, 2026
Code last changedi
Nov 19, 2026
Maker
WJDdidi-1
Packages
npm: ci-triage-cli
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account WJDdidi-1, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wjddidi-1-ci-triage.svg)](https://mcp.popnx.com/en/servers/wjddidi-1-ci-triage)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6182 servers in this category
  • Published to the registry more recently than 91% of the other 6182 servers in this category
  • Basic checks equal to or better than 99% of the other 6182 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ci-triage safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.1.2) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
ci-triage
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseApache-2.0MITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ci-triage

CI is red. Which failure matters, and is it a real regression or just flaky?

ci-triage answers that in one page: it fetches a repo's recent failed GitHub Actions runs, reads the failed job logs, groups failures by root cause, and tells you which ones are real regressions and which are flaky — so you fix the one thing that matters instead of reading thousands of log lines by hand.

Before / after

Before: CI is red on 3 runs. You open each run, find the failed job, scroll through the log, and try to remember whether you saw this error yesterday.

After:

$ ci-triage acme/widgets

ci-triage — acme/widgets Window: 2 recent runs listed, 2 failed examined Root causes: 1 (1 real, 0 flaky)

#1 test · 2 runs · real regression FAIL src/components/Button.test.tsx 3 test-runner failure signals in the error lines. fails on every recent run — looks like a real regression, not flakiness. first seen 2026-11-12 10:00 · last seen 2026-11-12 14:03 runs: #2 (test), #1 (test) evidence: FAIL src/components/Button.test.tsx ● Button › renders the disabled state expect(received).toBe(expected) // Object.is equality

Overall: 1 root cause — 1 real regression, 0 flaky

One root cause, two runs, real regression, with the failing test named. That is the whole triage.

Install

npm install -g ci-triage-cli

Requires Node 18 or newer. No other dependencies — pure Node.js standard library.

Rather not install it by hand? Paste this to your coding agent: "Install ci-triage (npm install -g ci-triage-cli if it's not on PATH), then run ci-triage --skill-generate so you triage red CI before reading any log."

Use

ci-triage <owner/repo>            # triage the last 10 failed runs

ci-triage acme/widgets --runs 3 # fewer runs, faster ci-triage acme/widgets --workflow ci.yml --branch main ci-triage acme/widgets --json # machine-readable output ci-triage acme/widgets --top 3 # show only the top 3 root causes ci-triage acme/widgets --report triage.md # Markdown report to paste into a PR, an issue, or an agent chat ci-triage acme/widgets --annotations # also emit ::error:: / ::warning:: annotations for GitHub Actions

--report writes the same Markdown the GitHub Action puts in the Step Summary — the ranked report, not machine JSON — so the file, the summary, and the terminal output never disagree. Under --json the confirmation goes to stderr, so stdout stays parseable. --annotations does the same job for the run's annotations panel: one workflow-command line per root cause (::error:: for a real regression, ::warning:: for flaky or unknown), capped at 10 per level — GitHub's own limit. When the log names the failing file with a line (src/utils/format.ts:18:7, a Jest stack frame), the annotation is pinned to that file and line, so it also shows in the PR's changed-files view, one click from the code; a bare filename, an absolute runner path, or a node_modules frame stays unpinned rather than pointing at the wrong file. Under --json the lines go to stderr, so stdout stays parseable.

Exit codes: 0 when no failed job turned up, or when every failure in the window is a recorded known failure; 1 when failures were found (including failures whose logs could not be read — the repo is not clean), 2 for a usage error or an API error.

Known failures

A failure the team already knows about and is living with should not re-alert as a real regression on every triage — it drowns the new regressions. Record it once, then triage against the record:

ci-triage acme/widgets --write-known .ci-triage-known-failures.json

ci-triage acme/widgets --known .ci-triage-known-failures.json

--write-known records the current clusters and merges with entries already in the file; --known marks the clusters the file covers as known failures instead of new regressions. Matching is by failure signature, so a known failure stays known when it moves to another workflow. The file holds signature hashes and headlines only, so it is safe to commit. A recorded failure that stops appearing is listed as "not seen in this window (possibly fixed)" — remove it from the file if it is fixed. The method is Playwright's test.fail(): a known bug that is still exercised, expected to fail, and noticed when it stops failing. In the Action, a triage with only known failures passes the step instead of failing it.

Shell completion for bash, zsh and fish: ci-triage completion bash prints a completion script generated from the same option list the CLI parses, so it can never suggest a flag the CLI rejects. Install it with, e.g. ci-triage completion bash > ~/.bash_completion.d/ci-triage, or source <(ci-triage completion bash) for a one-off session. Mistyped a flag anyway? The CLI suggests the closest match (Did you mean ...?) instead of a bare error.

Auth — read this first

Set GH_TOKEN (or GITHUB_TOKEN). Without a token the triage can list the failed runs and jobs, but it cannot download their logs: GitHub does not allow anonymous job-log downloads, even for public repos. The first refused download stops the rest — the refusal applies to every job, so the triage lists all the failed jobs with the same reason instead of spending the anonymous budget on downloads known to fail. Without a token you get an honest report instead of a triage:

No clusters: 9 failed jobs found, but their logs could not be read.

Failed jobs #41–#49 · 2026-11-14 12:03 – 2026-11-15 08:41 Reason: downloading this job log needs a GitHub token (403) — GitHub does not allow anonymous log downloads; set GH_TOKEN or run gh auth login Overall: UNKNOWN — 9 failed jobs found, logs unreadable

With a token you get 5,000 API requests per hour. gh auth login works too when the GitHub CLI is logged in.

ci-triage doctor checks the setup itself before you triage anything: Node version, ci-triage on PATH, the home directory --skill-generate writes into, installed skills (and whether their frontmatter is valid — a broken one silently never triggers), whether a token is available, and whether the GitHub API answers (one cheap call, which also reports the rate-limit budget left this hour). It is read-only — it changes nothing — and every failure comes with a copy-paste fix. Warnings are for optional wiring (a missing skill, no token, an unreachable API); only failures make it exit 1. --json gives the same checklist as data. The method is Claude Code's claude doctor: one command that answers "is my setup healthy?" instead of debugging each piece by hand.

How it decides

  • Signature: the error lines of a failed job, with timestamps, ANSI codes, file paths, hashes, versions and counts stripped — so the same failure on two runs has the same signature even when the paths and timings differ.
  • Clustering: failures with the same signature are one root cause, ranked by how many runs they hit.
  • Classification: each cluster is a test failure, a build failure, or an infra failure (timeouts and the like), from the error lines themselves.
  • Flaky vs real: a cluster is flaky when the same commit passed on a later run, or when failures and successes alternate in the window. Failing on every recent run is a real regression.
  • Known failures: a cluster whose signature is recorded in a known-failures file (--known) is reported as a known failure, not a new regression. A triage with only known failures exits 0.
  • Regression window: a real regression names the last green run and the first red one ("broke between #1 (ccc0000) and #2 (aaa0000)"); git log .. lists the suspect commits. The method is git bisect's — the good and bad endpoints — answered from the run history instead of a binary search, since CI already ran every commit's build. The report also lists the files that changed between those two commits (GitHub's compare endpoint, capped at 10 with a count of the rest), so the fix starts from the suspect files, not just the suspect range; a compare that fails leaves the window line as it was. A flaky failure has no window; when no passing run precedes the first failure, the report says the regression predates the runs listed.

Logs expire: GitHub keeps job logs for 90 days. A failed job whose log is gone is recorded, not fatal.

For agents

ci-triage --mcp               # stdio MCP server: triage_repo, triage_log

ci-triage --skill-generate # write a SKILL.md for this project (never overwrites) and a short section in AGENTS.md ci-triage --skill-generate --agents # same skill, in .agents/skills/ — the shared location Gemini CLI and Codex discover skills from

triage_log classifies a pasted log without touching the network — useful when you already have the log open. Both tools return the same JSON the CLI's --json produces, as the text block and again as structuredContent, the MCP structured-output channel (each tool declares a loose outputSchema: { type: 'object' }; error results carry none), so a calling application can read the fields typed instead of parsing the text.

The MCP server also serves one prompt, triage_ci (prompts/list / prompts/get): the one-shot "what broke in CI and what do I fix first?" workflow — call triage_repo with the repo (and workflow, if given), report the root causes ranked real regressions first, then flaky, then unknown, then known failures, and do not re-run or fix anything without the user agreeing — for MCP clients that let the user pick a prompt instead of typing a request. The method is FastMCP's: prompts are the third MCP primitive, the user-invoked template next to tools and resources. triage_repo also takes knownFile: a known-failures file to mark recorded clusters as known instead of new regressions.

Claude Code users can install the skill without installing the CLI first: /plugin marketplace add WJDdidi-1/ci-triage, then /plugin install ci-triage@ci-triage. The skill lives in this repo at skills/ci-triage/SKILL.md, so skill indexes can find it too.

Claude Desktop: the repo ships a manifest.json (MCPB, the renamed DXT format) — pack it with npx @anthropic-ai/mcpb pack and drag the .mcpb file onto Settings → Extensions. The bundle is just the server (zero dependencies, so there are no node_modules to bundle), and .mcpbignore keeps tests and tooling out of it.

GitHub Action

Use it from a workflow (it needs a token with actions:read on the repo; the workflow's own GITHUB_TOKEN can read its own repo's runs):

jobs:

triage: runs-on: ubuntu-latest steps:

  • uses: WJDdidi-1/ci-triage@main with: repo: ${{ github.repository }} runs: 10

The action fails the job when it finds root causes, so the triage report lands in the log and in the run's Step Summary. Add --annotations to surface each root cause on the run's annotations panel too — one ::error:: per real regression, ::warning:: for flaky, unknown, or known — so the cause is visible without opening the log at all. It needs no token and no file, and it works on fork PRs, where the Checks API cannot write; the same trick reviewdog's github-annotations reporter uses. Locally it is a no-op: the lines only become annotations when a step runs in GitHub Actions.

How fast is it

On a real repo with 3 failed runs and 9 failed jobs, the triage took about 8 seconds wall-clock — against opening 9 job logs by hand and reading them. The clustering and classification themselves run in milliseconds; the time is the GitHub API round-trips.

Development

npm test            # node:test, no extra dependencies, run serially

node scripts/bump-version.mjs # bump every version pin at once

Coverage uses Node's built-in runner (Node 22+ only — the suite itself runs on Node 18+): `node --test --test-concurrency=1 --experimental-test-coverage --test-coverage-include='lib/**/*.mjs' --test-coverag

Only the beginning is shown; read the rest in the repo