gh-ci-triage
Triage failing PR checks with gh CLI, identify first actionable root cause, and derive exact local repro commands.
Best use case
gh-ci-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Triage failing PR checks with gh CLI, identify first actionable root cause, and derive exact local repro commands.
Teams using gh-ci-triage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gh-ci-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gh-ci-triage Compares
| Feature / Agent | gh-ci-triage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Triage failing PR checks with gh CLI, identify first actionable root cause, and derive exact local repro commands.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## 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
Related Skills
github-issue-triage
Analyze GitHub issues for the Nx repository and provide assignment recommendations based on technology stack, team expertise, and priority classification rules.
SAST Triage
Triage static analysis findings from gosec, golangci-lint, and govulncheck — classify severity, filter false positives, and prioritize remediation
pr-triage
Go through open pull requests, check their status, and take actions to move them forward. This includes triaging PRs, fixing CI, resolving feedback, merging, or managing PR workflow. Use when asked to triage PRs, go through open PRs, or manage PR workflow.
email-triage-draft-replies
Review unread email, categorize it, and draft replies (no sending without approval)
Tech Debt Triage
Score, prioritize, and plan technical debt remediation
Triage Workflow
This skill provides standardized workflows for rapid incident triage and initial assessment. For comprehensive triage procedures, decision trees, and real-world scenarios, please refer to the main **I
bgo
Automated Blender build-go workflow. Automatically builds, removes old version, installs, enables, and launches Blender with your extension/add-on. Use when you want to quickly test changes, execute complete build-to-launch cycle, or run custom packaging scripts with automatic Blender launch.
github-search
Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.
github-repo-skill
Guide for creating new GitHub repos and best practice for existing GitHub repos, applicable to both code and non-code projects
github-repo-analysis
Analyze GitHub repositories to extract insights about commit frequency, outstanding contributors, release timeline, and project health metrics. Use when users request repository analysis, commit history investigation, contributor identification, release tracking, or development activity assessment for any GitHub project.
github-pr-review-comments
Comprehensive workflow for managing GitHub PR review comments using gh CLI and GraphQL API. Use when asked to address review comments, find unreplied comments, reply to review threads, or resolve/unresolve review conversations. Supports finding ALL comments across pagination boundaries, replying to threads, and resolving conversations.
github-navigator
GitHub operations via gh CLI. CRITICAL: Always use instead of WebFetch for ANY github.com URL. Use when user provides GitHub URL, says 'facebook/react', 'show README', 'list issues', 'check PR', 'clone repo', 'analyze this repo', 'understand the architecture', 'how is X structured', 'explore the codebase'. For deep analysis of external repos, clones locally.