pr-expert

Diagnose failing pull request checks across GitHub Actions and external status providers.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill pr-expert-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-expert
Source: https://github.com/alkampfergit/cisharpai/tree/main/.github/skills/pr-expert
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill pr-expert-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests often show red checks even when CI workflows pass, leaving developers unsure which check is blocking merge or what file to fix. This Skill traces failing PR checks to their exact root cause, whether they come from GitHub Actions or external providers like SonarCloud and CodeQL. ## Core Features & Use Cases - Check Triage: Lists every check attached to the PR head commit and separates github-actions checks from external app statuses. - Provider-Specific Playbooks: Includes dedicated diagnostic workflows for SonarCloud quality gates and CodeQL security results, querying provider APIs directly rather than relying on GitHub summaries. - Root Cause Mapping: Identifies the exact rule, severity, file, and line behind a failure and recommends the smallest correct fix. - Use Case: A PR is red even though the SonarCloud workflow job passed. The Skill queries the SonarCloud PR analysis, finds a vulnerability from rule githubactions:S8233 caused by workflow-level write permissions in .github/workflows/ci.yml, and recommends moving permissions to job level. ## Quick Start Ask the assistant to diagnose why your pull request is failing and identify which check is blocking merge and what file needs to change.

Frequently Asked Questions about pr-expert

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

FAQPage Schema
How do I find out why my pull request is failing?▼

List every check attached to the PR head commit, record each check's owner and conclusion, then inspect the failing provider directly. The failing check may come from an external app like SonarCloud rather than a GitHub Actions job.

Why is my PR red when all GitHub Actions workflows passed?▼

A red PR with green workflows usually means an external app published a failing status on the head commit. Query providers like SonarCloud or CodeQL directly for PR-specific quality gate or security results instead of reading workflow logs.

How do I diagnose a SonarCloud quality gate failure on a pull request?▼

Fetch the PR entry from SonarCloud using the project key and PR number, read the qualityGateStatus and issue counts, then query issues filtered by type such as VULNERABILITY. Capture the rule key, severity, file, and line, and verify the finding against the repository code.

Why does branch protection say a required status check is missing?▼

The required check name may not match the actually reported check name, or the check never ran on the head SHA. Compare the branch protection requirement with the check suite attached to the PR head commit.

Can this skill fix the failing code automatically?▼

No, the skill focuses on diagnosis only: naming the failing check, its owner, the root cause, the affected file and line, and the minimal fix recommendation. Implementing the code fix is out of scope unless explicitly requested as follow-up work.