Skip to content
Back to skills

Pr Summary

ASecurity

Summarize accessible open GitHub pull requests from structured gh JSON, filtering bots and grouping results by ticket. Use for a read-only PR status report. Not for: changing PR state, reviewing code, merging, or closing PRs. Output: grouped Markdown written to /tmp/pr-summary.md and displayed for copying.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentsgitapi

Works with

  • terminal
  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add hmj1026/dhpk --skill pr-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pr Summary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pr Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hmj1026-pr-summary/badge)](https://www.skillsdirectory.com/skills/hmj1026-pr-summary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pr-summary
description: 'Summarize accessible open GitHub pull requests from structured gh JSON, filtering bots and grouping results by ticket. Use for a read-only PR status report. Not for: changing PR state, reviewing code, merging, or closing PRs. Output: grouped Markdown written to /tmp/pr-summary.md and displayed for copying.'
argument-hint: '[--author=<user>] [--label=<label>]'
metadata:
  dhpk-invocation-class: implicit-eligible
---

# PR Summary

## Workflow

Run in the consumer repository and preserve `--author <user>` and
`--label <label>`. Resolve the repository with `gh repo view`, then query open
PRs with `gh pr list --json ...`; consume structured JSON rather than scraping
terminal formatting. Stop when `gh` is unavailable, the repository query
fails, or the PR query fails.

Filter bot-authored PRs, group the remaining records by ticket ID (including
stacked PR annotations), format the report, write the same report to
`/tmp/pr-summary.md`, and display it with copy instructions. The exact JSON
fields and grouping rules are in
[`references/workflow.md`](references/workflow.md). This workflow never
changes GitHub state.

## When NOT to Use

- A PR must be created, edited, merged, closed, or labeled.
- A code review or merge-readiness verdict is requested.
- `gh` repository credentials or access are unavailable.

## Output

Formatted open-PR groups with ticket IDs and stacked-PR annotations, plus the
path `/tmp/pr-summary.md` and copy instructions. An empty result is a valid
report. Query or report-write failures are terminal `UNAVAILABLE`/`FAIL`
results and must be surfaced.

## Verification

- [ ] Repository and PR data came from successful structured `gh` JSON calls.
- [ ] `--author`/`--label` filters were preserved and bot PRs were handled.
- [ ] Every included PR appears in exactly one ticket group (or an explicit
      `unassigned` group).
- [ ] `/tmp/pr-summary.md` exists and matches the displayed report.

## References

- [`references/workflow.md`](references/workflow.md) — `gh` fields, filters,
  bot exclusion, ticket grouping, and report format.

Files in this skill

  • SKILL.md2.1 KB
  • agents/openai.yaml189 B
  • references/workflow.md1.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.