How do I install the Gh Pr Results Review skill?

Run npx skillmds@latest add soundblaster/gh-pr-results-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Pr Results Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Pr Results Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Pr Results Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Pr Results Review?

SoundBlaster (@soundblaster) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Pr Results Review by soundblaster

Name: Gh Pr Results Review
Rating: 4.5 (4 reviews)
Author: SoundBlaster

Gh Pr Results Review

Review GitHub pull request CI outcomes with the GitHub CLI and extract actionable failure details from GitHub Actions logs. Use when asked to check failing PR checks, inspect lint/test/type-check errors, identify failing jobs, or summarize why a PR pipeline failed and what to fix first.

SoundBlaster Updated Sep 10, 2026

File contents

GH PR Results Review

Workflow

Identify the PR number and check status.

Run:

gh pr checks <pr-number> 2>&1

Capture failing checks, durations, run URL, and job URLs.
If no failures exist, report success and stop.

Resolve run and failing job IDs.

Derive the workflow run ID from the run URL when available.
Derive each failing job ID from job URLs, or list jobs with:

gh run view <run-id> --json jobs

Pull logs for failed jobs.

For each failed job:

gh run view <run-id> --job <job-id> --log 2>&1 | tail -80

If the tail misses the error, inspect more lines or grep for error markers:

gh run view <run-id> --job <job-id> --log 2>&1 | rg -n "error|failed|traceback|E999|F401|mypy|pytest"

Summarize root causes with evidence.

Report by failing check/job name.
Include the shortest exact evidence line(s) that explain failure.
State likely fix direction (for example: ruff import ordering, mypy type mismatch, failing pytest assertion).

Output Format

Use this structure:

check the CI failure details.

Reviewed GitHub Actions logs for test and linting results
Bash
gh pr checks <pr-number> 2>&1
<key failing checks output>

Bash
gh run view <run-id> --job <job-id> --log 2>&1 | tail -60
<relevant error/failure excerpt>

Bash
gh run view <run-id> --job <job-id> --log 2>&1 | tail -40
<relevant error/failure excerpt>

Then provide a short diagnosis section:

Finding: one sentence per failed job.
Evidence: command + key line.
Next fix: concrete first edit to attempt.

Guardrails

Do not claim a job failed without a log line proving it.
Prefer job-specific logs over workflow-level summaries.
Keep excerpts tight; include only lines needed to justify the finding.
If GitHub CLI lacks permission or run is missing, state the blocker and requested access explicitly.

---name: gh-pr-results-reviewdescription: Review GitHub pull request CI outcomes with the GitHub CLI and extract actionable failure details from GitHub Actions logs. Use when asked to check failing PR checks, inspect lint/test/type-check errors, identify failing jobs, or summarize why a PR pipeline failed and what to fix first.---# GH PR Results Review## Workflow1. Identify the PR number and check status.- Run:```bashgh pr checks <pr-number> 2>&1```- Capture failing checks, durations, run URL, and job URLs.- If no failures exist, report success and stop.2. Resolve run and failing job IDs.- Derive the workflow run ID from the run URL when available.- Derive each failing job ID from job URLs, or list jobs with:```bashgh run view <run-id> --json jobs```3. Pull logs for failed jobs.- For each failed job:```bashgh run view <run-id> --job <job-id> --log 2>&1 | tail -80```- If the tail misses the error, inspect more lines or grep for error markers:```bashgh run view <run-id> --job <job-id> --log 2>&1 | rg -n "error|failed|traceback|E999|F401|mypy|pytest"```4. Summarize root causes with evidence.- Report by failing check/job name.- Include the shortest exact evidence line(s) that explain failure.- State likely fix direction (for example: ruff import ordering, mypy type mismatch, failing pytest assertion).## Output FormatUse this structure:```textcheck the CI failure details.Reviewed GitHub Actions logs for test and linting resultsBashgh pr checks <pr-number> 2>&1<key failing checks output>Bashgh run view <run-id> --job <job-id> --log 2>&1 | tail -60<relevant error/failure excerpt>Bashgh run view <run-id> --job <job-id> --log 2>&1 | tail -40<relevant error/failure excerpt>```Then provide a short diagnosis section:- `Finding`: one sentence per failed job.- `Evidence`: command + key line.- `Next fix`: concrete first edit to attempt.## Guardrails- Do not claim a job failed without a log line proving it.- Prefer job-specific logs over workflow-level summaries.- Keep excerpts tight; include only lines needed to justify the finding.- If GitHub CLI lacks permission or run is missing, state the blocker and requested access explicitly.

Frequently asked questions