菜单
Build a review-oriented Markdown (or JSON) report for a list of GitHub PRs: links, title, description excerpt, CI rollup status, line and file stats, and optional unified diffs. Use when the user pastes multiple PR URLs, asks for a PR batch table, "review these PRs", or wants CI/diff summaries across several pulls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
ObsInt Processing team reference — repos, services, deployment, clusters, shared coding standards, PR rules, and language conventions. Shared guidance for team repositories; repo-specific details live in each repo's AGENTS.md.
Generate a report of what you have worked on in a given quarter. The Quarterly Connection is something all Red Hat users must complete after a quarter has ended. There you talk what you have accomplished, the goals you had and the goals you want to set up for the next quarter. Most of this information is already in Jira, so we can use that to generate the report and help the user remember what they have done in those months. This should be used when the user asks for help writing the quarterly connection on Workday.
Collect GitHub PRs and GitLab MRs authored by a user during a given quarter. Produces a themed report of code contributions across team repositories. Use alongside the quarterly-connection-jiras skill to complement Jira-based reports with actual code work, or standalone when the user asks for a PR/MR summary.
Triage CCX rule release pipeline failures — identifies failed stage/job, classifies root cause, and suggests a fix.
Triage Glitchtip-sourced Jira tickets in the CCXDEV project — detect duplicates, investigate root causes via stack traces and source code, and post "[AI suggestion]" comments. Use this skill whenever the user mentions triaging Glitchtip errors, reviewing ccx-processing/obsint-processing Jira tickets, deduplicating error reports, or investigating production/staging errors tracked in Jira with the glitchtip label.
Generate the weekly Processing team Scrum of Scrums report from Jira epics. Compares progress over the last 7 days (report day is usually Wednesday): child-task movement, epic completion %, and epic status updates. Use when the user asks for a scrum of scrums, SoS report, weekly epic status, processing epic report, or Wednesday status report.
| name | pr-batch-report |
| description | Build a review-oriented Markdown (or JSON) report for a list of GitHub PRs: links, title, description excerpt, CI rollup status, line and file stats, and optional unified diffs. Use when the user pastes multiple PR URLs, asks for a PR batch table, "review these PRs", or wants CI/diff summaries across several pulls. |
Produces a single document summarizing many pull requests using
the GitHub CLI (gh). Each row includes the PR link, title, a short
description excerpt, a coarse CI label from statusCheckRollup,
additions/deletions/total touched lines, file count, and paths inferred
from gh pr diff.
gh installed and authenticated:
gh auth statusgithub.comFrom the repository root (or any directory):
python3 skills/pr-batch-report/scripts/pr_batch_report.py \
'https://github.com/org/repo/pull/1' \
'https://github.com/org/repo/pull/2/changes'
URLs may include a trailing /changes segment; it is stripped.
Input from a file (one URL per line; # starts a comment):
python3 skills/pr-batch-report/scripts/pr_batch_report.py --file urls.txt
Stdin (when no positional URLs and no --file, non-TTY stdin is read):
cat urls.txt | python3 skills/pr-batch-report/scripts/pr_batch_report.py
| Flag | Description |
|---|---|
--format markdown | Default. Emits a GitHub-flavored Markdown report. |
--format json | Machine-readable array of objects (includes diff unless --no-diff). |
--no-diff | Skip gh pr diff (faster; path column stays empty in markdown). |
--diff-mode inline | Print each diff in a fenced diff block (default). |
--diff-mode collapse | Wrap each diff in <details><summary>…</summary> (renders on GitHub). |
--diff-mode none | Table + CI notes only; still fetches diffs unless --no-diff (for path hints). |
--max-desc N | Truncate description excerpts in the table (default: 240). |
-j N | Parallel gh calls (default: 8). |
# Compact table, no patch bodies
python3 skills/pr-batch-report/scripts/pr_batch_report.py --no-diff -f urls.txt
# GitHub-friendly long report with collapsible diffs
python3 skills/pr-batch-report/scripts/pr_batch_report.py --diff-mode collapse -f urls.txt > report.md
gh auth status works for the target org (e.g. RedHatInsights)./changes if present (the script does this automatically).--diff-mode collapse when the list is large so the chat or issue stays readable.passing means no failed or in-progress checks in that rollup; NEUTRAL / SKIPPED on individual jobs are not treated as failures.failing or pending, call out those PRs first.gh pr review --approve.The script classifies rollup entries from gh pr view --json statusCheckRollup:
failing — any CheckRun with conclusion in
FAILURE, ERROR, TIMED_OUT, CANCELLED, ACTION_REQUIRED,
or a StatusContext with state FAILURE.pending — any check still IN_PROGRESS, PENDING, QUEUED, etc.passing — otherwise (including completed SUCCESS, SKIPPED, NEUTRAL).This matches a quick human review but does not know branch-protection required-check rules; use the GitHub UI for authoritative merge gating.
gh pr view and gh pr diff.-j modestly if you hit throttling.--diff-mode collapse with selective URLs or --no-diff for overview-only passes.