comet-github-ci-triage

Diagnose failing GitHub Actions and Codecov checks on Comet pull requests.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-github-ci-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-github-ci-triage
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-github-ci-triage
Command: npx skills add https://github.com/rpamis/comet --skill comet-github-ci-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a Comet pull request shows red CI checks, it is hard to tell whether the failure comes from production code, test fixtures, toolchain drift, stale runs, or coverage thresholds. This Skill performs evidence-based triage of GitHub Actions and Codecov results so you know the real root cause before attempting any fix.

Core Features & Use Cases

  • Accurate Remote State Inspection: Resolves the PR's current head SHA, runs gh pr checks, and inspects failed job logs with gh run view --log-failed instead of trusting aggregated summaries.
  • Failure Classification: Categorizes red results into production code, test fixtures, generated runtime drift, toolchain/platform issues, credentials, stale checks, or unresolved coverage thresholds.
  • Codecov Verification: Uses available APIs to check affected files and patch coverage metadata when the Codecov page is incomplete.
  • Use Case: A Comet PR shows a failing job and a Codecov warning. Use this Skill to confirm the checks belong to the current head, extract the real failure boundary from logs, and report the root cause with minimal next actions.

Quick Start

Use the comet-github-ci-triage skill to find the real cause of the failing CI checks on my Comet pull request.

Frequently Asked Questions about comet-github-ci-triage

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

FAQPage Schema
How do I find the real cause of a failing GitHub Actions check on a PR?

Run gh pr checks to list check states, then use gh run view with --log-failed on the failing run to inspect actual job logs. This Skill verifies the checks belong to the current head SHA before trusting any failure summary.

How to triage Codecov patch coverage failures on pull requests?

Check the affected files and patch coverage metadata through the available Codecov APIs when the web page is incomplete. Report the exact head SHA and coverage scope, and treat unresolved coverage thresholds as a distinct failure category.

Why does a PR show failing checks that do not match my local code?

The displayed checks may belong to an outdated head commit rather than the current code. Stale runs cannot prove the current code is broken, so always confirm the check's head SHA matches the PR's latest commit before diagnosing.

Does this Skill automatically fix CI failures it finds?

No, it performs diagnosis only by default. Fixes are implemented only when the user explicitly requests them, and confirmed scopes are handed to the comet-github-issue-fix and comet-safe-delivery skills after authorization.

What failure categories does CI triage distinguish?

It classifies failures into production code, test fixtures or frozen contract projections, generated runtime drift, dependency or toolchain issues, credentials and runner configuration, stale checks or merge conflicts, and unresolved coverage thresholds.