Skip to content
Back to skills

Gh Ci Triage

ASecurity

Triage failing PR checks with gh CLI, identify first actionable root cause, and derive exact local repro commands.

  • 57 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 31, 2026
researchrustrailsgit

Works with

  • cli

Security analysis

A100/100

Scanned May 31, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill gh-ci-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gh Ci Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gh Ci Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-gh-ci-triage/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-gh-ci-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gh-ci-triage
description: Triage failing PR checks with gh CLI, identify first actionable root cause, and derive exact local repro commands.
license: Apache-2.0
compatibility: opencode
metadata:
  project: up-streamer-rust
  workflow: ci-triage
---

## When to use

Use this skill when a PR reports failing GitHub checks and you need a fast, evidence-backed diagnosis.

## Workflow

1. Fetch check overview:
   - `gh pr checks <pr-number>`
   - `gh pr view <pr-number> --json statusCheckRollup`
2. Inspect failed jobs only:
   - `gh run view <run-id> --log-failed`
   - If needed, `gh run view <run-id> --job <job-id> --log-failed`
3. Extract first actionable error (not cascaded noise).
4. Map failure to local repro command using the exact workflow flags.
5. After fix, rerun local repro commands before pushing.
6. Re-check status:
   - `gh pr checks <pr-number>`

## Guardrails

- Do not assume root cause from PR title/last commit; use failed logs.
- Distinguish no-feature lint failures from feature-enabled failures.
- Prefer minimal-scope fixes; avoid broad suppression (`#[allow(...)]`) unless required.

## Report template

Always report:

1. Failing workflow/job name
2. First actionable error line(s)
3. Root cause hypothesis
4. Exact local repro command
5. Fix applied
6. Post-fix local verification commands and results

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.