New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Parallel CI Triage

by spencerpauly in spencerpauly/awesome-cursor-skills

When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.

CC0-1.0Auto-check passedDevOps & Cloud

Install Parallel CI Triage

skills CLI
$ npx skills add spencerpauly/awesome-cursor-skills --skill parallel-ci-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install spencerpauly/awesome-cursor-skills parallel-ci-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/parallel-ci-triage .claude/skills/parallel-ci-triage && rm -rf skills-src

Use ~/.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/

Facts

Skill name
parallel-ci-triage
GitHub stars
844
Token cost
~793 tokens
SKILL.md length
333 words
Files
1
Skills in repo
60
Repo updated
First seen
Licence
CC0-1.0

At a glance

When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.

  • Works in 4 steps: Identify the failing run → Split by job (or by failure cluster) → Launch parallel subagents → …
  • Multi-job CI failures where jobs are independent
  • SKILL.md covers Prerequisites, Workflow, When to use and When not to use, plus 1 more section
  • Calls gh and npm

What it does

Parallel CI Triage is an agent skill from spencerpauly/awesome-cursor-skills. When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Subagents, Failing and flaky tests and CI/CD. It works with GitHub Actions and GitHub. The repository describes itself as: A curated list of awesome skills for Cursor. The licence is CC0-1.0.

When your agent uses it

  • Multi-job CI failures where jobs are independent
  • Tasks that involve Subagents
  • Tasks that involve Failing and flaky tests

Example prompts

  • “/parallel-ci-triage”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify the failing run
  2. Split by job (or by failure cluster)
  3. Launch parallel subagents
  4. Merge and verify

What it can do on your machine

Read from SKILL.md and the folder at commit 99cd265. 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

    Shell commands in SKILL.md call:

    • gh
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and npm, which can reach the network depending on how they are called.

    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

Parallel CI Triage loads about 793 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 333 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~793

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

The full file from spencerpauly/awesome-cursor-skills at commit 99cd265, republished under its CC0-1.0 licence (© spencerpauly). 333 words, ~793 tokens.

Download SKILL.mdSave it as .claude/skills/parallel-ci-triage/SKILL.md (or your agent's skills folder).
name
parallel-ci-triage
description
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
user-invocable
true

Parallel CI Triage

Speed up fixing broken CI by splitting failing jobs (or independent failure clusters) across parallel subagents. Each subagent owns one vertical slice: logs, root cause, code fix, and local verification for that slice.

Prerequisites

  • GitHub CLI (gh) installed and authenticated (gh auth login), or use the GitHub web UI / API to copy logs manually.
  • Push access to the repo so fixes can be pushed and CI re-run.

Workflow

1. Identify the failing run

From the repo root:

bash
gh run list --limit 5
gh run view <RUN_ID> --log-failed

Or open the Actions tab, open the failed workflow run, and note which jobs failed (not just which step — group by job name).

If gh is unavailable, download logs from the GitHub UI and paste them into the conversation.

2. Split by job (or by failure cluster)
  • One subagent per failed job when jobs test different things (e.g. lint, test-node-18, e2e).
  • One subagent per independent failure cluster when a single job logs multiple unrelated errors — but prefer one job per agent to avoid conflicting edits in the same files.

If two failures share the same root cause in the same file, assign one subagent to fix both.

3. Launch parallel subagents

For each failing job, launch a generalPurpose subagent in a single message so they run concurrently:

Task: Fix CI failure for job "<JOB_NAME>"

Context:
- Workflow run: <RUN_URL or RUN_ID>
- Branch: <branch>
- Relevant log excerpt (failed steps only):
<paste gh run view --job <JOB_ID> --log or the failed section>

Instructions:
1. Infer the root cause from the log (command, stack trace, file:line).
2. Open and edit only what this job requires.
3. Run the same commands locally that failed in CI (or the narrowest equivalent, e.g. `npm run lint`, `pytest tests/foo`, `pnpm test --filter pkg`).
4. Report: what failed, what you changed, and confirmation that the local command passes.

Include the exact failing command and error lines so the subagent does not guess.

4. Merge and verify

  • Collect each subagent’s changed files. Resolve overlaps manually if two agents touched the same file.

  • Run the full CI-equivalent locally when possible:

    bash
    # Example: match your repo
npm run lint && npm test

  • Commit with a conventional message, push, and re-check the workflow:

    bash
    gh run watch

When to use

  • Multiple GitHub Actions jobs failed and the failures look independent.
  • A long workflow log is easier to split by job than to fix sequentially.

When not to use

  • A single job with one clear error — fix it in the main agent.
  • Failures that are purely flaky infrastructure — retry or fix workflow config first.

Notes

  • Redact secrets if pasting logs into chat.
  • If agents conflict on shared files, merge sequentially after the parallel pass.

© spencerpauly, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/parallel-ci-triage of spencerpauly/awesome-cursor-skills.

Open the folder on GitHubat commit 99cd265

Compare with similar skills

Parallel CI Triage 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.

Parallel CI Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Parallel CI Triage this skillspencerpauly/awesome-cursor-skills844—~793Automated safety check: PassCC0-1.0
CI Watchdoglatitude-dev/latitude-llm4.7k—~1.6kAutomated safety check: PassMIT
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
Gh Fix CIJetBrains/skills3667 repos~953Automated safety check: PassApache-2.0
Openai Gh Fix CItrailofbits/skills-curated513—~955Automated safety check: NotesCC-BY-SA-4.0
ONNX Runtime CI Managementmicrosoft/onnxruntime22k—~4.1kAutomated safety check: PassMIT

Similar skills

  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Megatron-LM CI Failure Triage

    NVIDIA/Megatron-LM

    Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Gh Fix CI

    JetBrains/skills

    Official

    A skill your agent uses when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and…

    366 GitHub starsUsed in 7 repos~953 tokens
    DevOps & CloudAuto-check passed

  • Openai Gh Fix CI

    trailofbits/skills-curated

    Official

    A skill your agent uses when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and…

    513 GitHub stars~955 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes

  • ONNX Runtime CI Management

    microsoft/onnxruntime

    Official

    Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.

    22k GitHub stars~4.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • CI/CD Failure Troubleshooting

    ruby-git/ruby-git

    Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed

More from spencerpauly/awesome-cursor-skills

All 60 skills in this repo

  • Generating Images

    spencerpauly/awesome-cursor-skills

    Generate or edit images using the OpenAI Image API (gpt-image-2).

    844 GitHub stars~3.7k tokensUpdated 2 mo ago
    Auto-check: notes

  • Babysitting PR

    spencerpauly/awesome-cursor-skills

    Monitor a pull request for CI failures, review comments, and merge conflicts — then fix them automatically.

    844 GitHub stars~930 tokensUpdated 2 mo ago
    Auto-check passed

  • Best Of N Solving

    spencerpauly/awesome-cursor-skills

    Solve a hard problem by trying multiple approaches in parallel using isolated git worktrees.

    844 GitHub stars~698 tokensUpdated 2 mo ago
    Auto-check passed

  • Grinding Until Pass

    spencerpauly/awesome-cursor-skills

    Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean.

    844 GitHub stars~796 tokensUpdated 2 mo ago
    Auto-check passed

  • Parallel Exploring

    spencerpauly/awesome-cursor-skills

    Explore a large codebase in parallel by launching multiple explore subagents that each investigate a different area simultaneously.

    844 GitHub stars~787 tokensUpdated 2 mo ago
    Auto-check: notes

  • Profiling Performance

    spencerpauly/awesome-cursor-skills

    Profile a running web application's CPU performance using Cursor's built-in browser profiler.

    844 GitHub stars~686 tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Parallel CI Triage

What does Parallel CI Triage do?

When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Parallel CI Triage is an agent skill from spencerpauly/awesome-cursor-skills. When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.

When should I use Parallel CI Triage?

Parallel CI Triage fits situations like: multi-job CI failures where jobs are independent; tasks that involve Subagents; tasks that involve Failing and flaky tests.

How do I install Parallel CI Triage in Claude Code?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill parallel-ci-triage -a claude-code`. Or copy the skill folder (resources/parallel-ci-triage in spencerpauly/awesome-cursor-skills) into .claude/skills/parallel-ci-triage in your project. Claude Code loads it when a task matches its description.

How do I install Parallel CI Triage in Codex?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill parallel-ci-triage -a codex`. Or copy the skill folder (resources/parallel-ci-triage in spencerpauly/awesome-cursor-skills) into .agents/skills/parallel-ci-triage in your project. Codex loads it when a task matches its description.

Can I use Parallel CI Triage 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 spencerpauly/awesome-cursor-skills --skill parallel-ci-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/parallel-ci-triage, .gemini/skills/parallel-ci-triage, .github/skills/parallel-ci-triage and .opencode/skills/parallel-ci-triage in your project.

What does Parallel CI Triage need to run?

Going by SKILL.md and its folder, Parallel CI Triage needs the command-line tools its instructions call (gh and npm).

Does Parallel CI Triage access the network?

SKILL.md contains no URLs. Its commands use gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Parallel CI Triage 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 Parallel CI Triage use?

Parallel CI Triage is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Parallel CI Triage use?

About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Parallel CI Triage?

Skills that share tags, products or a category with Parallel CI Triage: CI Watchdog (latitude-dev/latitude-llm, 4.7k stars), Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars), Gh Fix CI (JetBrains/skills, 366 stars) and Openai Gh Fix CI (trailofbits/skills-curated, 513 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Parallel CI Triage?

spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 844 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on August 2, 2026.

Source: spencerpauly/awesome-cursor-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.