ci-triage

Diagnose red or stuck GitHub Actions CI runs for the brepjs repository.

77|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/andymai/brepjs --skill ci-triage-andymai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-triage
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/ci-triage
Command: npx skills add https://github.com/andymai/brepjs --skill ci-triage-andymai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging red or stuck GitHub Actions CI runs for the brepjs project is time-consuming without deep knowledge of the repository's custom CI configuration, job dependencies, and common failure modes unique to its codebase.

Core Features & Use Cases

  • Comprehensive failure mapping: Documents every known CI job failure mode, from npm ci lockfile sync errors and test shard timeouts to publish workflow auth issues and docs deployment gate failures, with exact root causes and step-by-step fixes.
  • Project-specific context: Includes critical brepjs CI quirks like release-please auto-merge hold logic, coverage job behavior, and unbaselined pattern violation recovery, so you don't have to reverse-engineer the workflow files yourself.
  • Use case example: If your PR's ci-pass job is red due to an EUSAGE error from a recent Dependabot bump, this skill provides the exact lockfile surgery steps to fix the issue without regenerating the entire lockfile.

Quick Start

Use the ci-triage skill to diagnose the failing ci-pass job on your brepjs pull request and get the exact fix for the reported error.

Frequently Asked Questions about ci-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix GitHub Actions CI failures for the brepjs JavaScript CAD library?

This skill diagnoses failing GitHub Actions CI runs for the brepjs JavaScript CAD library project, providing actionable, project-specific recovery recipes for every documented CI failure mode including PR check failures and publish workflow errors.

Why does the npm ci lockfile sync fail on my Dependabot PR?

The npm ci lockfile sync failure on a Dependabot PR is caused by an EUSAGE error from a dependency bump. You can fix it by applying targeted lockfile surgery steps without regenerating the entire lockfile.

How do I resolve test shard timeouts in GitHub Actions?

To resolve test shard timeouts in GitHub Actions, this skill provides exact root causes and step-by-step fixes for timeout scenarios specific to the brepjs repository's custom CI configuration and job dependencies.

Does this CI triage skill cover release-please auto-merge hold logic and deployment gate issues?

Yes, this CI triage skill covers release-please auto-merge hold logic, docs deployment gate failures, and publish workflow auth issues, so you don't have to reverse-engineer the workflow files yourself.

What is the best way to recover from unbaselined pattern violations in CI?

The best way to recover from unbaselined pattern violations in CI is to apply the project-specific recovery steps provided by this skill, which documents the exact fixes for coverage job behavior and pattern violation errors.