getting-pr-workflow-results

Summarize GitHub PR workflow job outcomes and generate gh log retrieval commands.

1|Updated Jul 14, 2017
One-click install
npx skills add https://github.com/karlmdavis/dotfiles --skill getting-pr-workflow-results
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: getting-pr-workflow-results
Source: https://github.com/karlmdavis/dotfiles/tree/main/private_dot_claude/skills/getting-pr-workflow-results
Command: npx skills add https://github.com/karlmdavis/dotfiles --skill getting-pr-workflow-results

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking GitHub PR workflow results, waiting for completion, and sifting through logs for errors is a tedious and time-consuming process. This Skill automates the entire process, providing a concise summary of job statuses and actionable commands to retrieve logs, saving you significant debugging time.

Core Features & Use Cases

  • Automated Waiting: Automatically waits for all PR workflows to complete, eliminating manual polling.
  • Job Status Summary: Provides a clear overview of which workflow jobs passed or failed.
  • Error Extraction: Extracts key error messages and test failures from logs of failed jobs, without loading full logs into context.
  • Log Retrieval Commands: Generates gh CLI commands to fetch full logs or specific job logs for deeper investigation.
  • Use Case: You've pushed a change and need to know if CI passed. Instead of constantly refreshing GitHub Actions, use this Skill to automatically wait for completion, then get a summary of any failures with direct commands to pull relevant logs.

Quick Start

Use the getting-pr-workflow-results skill for PR number 456 to get a summary of all workflow job outcomes and any detected errors.

Frequently Asked Questions about getting-pr-workflow-results

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

FAQPage Schema
How do I check if my GitHub PR workflow passed without manually refreshing?

Automated PR workflow monitoring waits for all GitHub Actions jobs to complete, then provides a summary of passed and failed statuses with error messages extracted from logs. This eliminates manual polling and saves debugging time by surfacing failures immediately.

Can I get error details from failed CI jobs without loading entire logs?

Yes. The Skill extracts key error messages and test failures from failed job logs and generates `gh` CLI commands to fetch full logs on demand, keeping your context lean while providing actionable debugging references.

How do I retrieve GitHub Actions logs for a specific PR job?

After workflow completion, the Skill returns ready-to-run `gh` commands that fetch full logs or artifacts for individual jobs, letting you dive into details only when needed without manual GitHub UI navigation.

What's the best way to automate CI/CD status checks for pull requests?

Automated workflow result monitoring waits for PR pipeline completion, reports job outcomes with extracted error context, and provides direct CLI commands for log retrieval, automating the entire status-checking process end-to-end.

Does this work with multi-job GitHub Actions workflows?

Yes. The Skill processes all workflow jobs in a PR, summarizing each job's pass/fail status and extracting errors from failed runs, providing a complete overview of complex multi-job pipelines.

When should I use workflow monitoring instead of checking GitHub directly?

Use automated workflow monitoring when you need rapid feedback on CI results, error context without sifting logs, and CLI commands for deeper investigation—especially for frequent PR reviews where manual checking creates bottlenecks.