pr-summary

Lists open GitHub PRs, filters automation bots, and groups them by ticket ID into Markdown.

189|25|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill pr-summary-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/pr-summary
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill pr-summary-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually reviewing dozens of open pull requests across a repository is tedious, especially when automation bots like Dependabot and Snyk clutter the list. This Skill produces a clean, ticket-grouped Markdown summary of open PRs so teams can quickly see what work is pending and how stacked PRs relate to each other. ## Core Features & Use Cases - Automated PR Aggregation: Fetches up to 200 open PRs via the GitHub CLI and filters out dependabot and snyk automation branches. - Ticket-Based Grouping: Extracts ticket IDs (e.g., PROJ-520) from branch names and groups related PRs, detecting stacked PRs whose base is a feature branch. - Use Case: Before a sprint standup, run the summary to get a Markdown digest of all open PRs organized by Jira ticket, with stacked dependencies annotated, ready to paste into Slack or a status doc. ## Quick Start Ask the assistant to run /pr-summary to generate a grouped Markdown summary of all open pull requests in the current repository.

Frequently Asked Questions about pr-summary

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

FAQPage Schema
How do I list and group open GitHub PRs by ticket ID?▼

Run the pr-summary script, which calls gh pr list to fetch open PRs, extracts ticket IDs like PROJ-520 from branch names, and groups matching PRs together. The grouped result is written as Markdown to /tmp/pr-summary.md.

How to filter out dependabot and snyk PRs from gh pr list?▼

The script automatically excludes any PR whose head branch starts with dependabot/ or snyk- using jq filters on the gh CLI output. No extra flags are needed; automation PRs are removed before grouping.

Can I filter the PR summary by author or label?▼

Yes, pass --author <user> or --label <label> to the script or the /pr-summary command. These flags are forwarded directly to gh pr list to narrow the fetched pull requests.

Does the PR summary detect stacked pull requests?▼

Yes, any PR whose base branch is not main, master, or develop is treated as stacked. Stacked PRs are grouped with their parent ticket and annotated with (stacked on <base branch>) in the output.

What happens if gh CLI is not installed?▼

The script checks for the gh command at startup and exits with an error message if it is missing. Install the GitHub CLI and authenticate it before running the summary.