gh-pr-results-review

You can identify failing GitHub PR checks by running `gh pr checks <pr-number> 2>&1`, which collects checks, runs, and logs to surface concise, evidence-backed failure summaries for quick remediation.

Yes, you can get a root-cause summary for lint or type-check failures by deriving the workflow run ID, retrieving logs for failing jobs, and producing a prioritized summary with concrete remediation steps.

Yes, the GitHub CLI is required to collect checks, runs, and logs. You derive the workflow run ID and failing job IDs from job URLs or by listing jobs to retrieve logs for failed jobs.

The best way to summarize PR CI failures with exact evidence lines is to use GitHub CLI commands to fetch logs and apply structured analysis to output concise, evidence-backed findings for quick remediation.

GitHub PR checks may fail without a clear UI error because the details are buried in Actions logs; retrieving logs for failed jobs surfaces the exact evidence lines needed for root-cause analysis.

You find the workflow run ID and failing job IDs by listing jobs or deriving them from job URLs within the GitHub PR checks output, allowing you to retrieve logs for failed jobs and extract actionable failure details.