ywc-release-pr-list

Name: ywc-release-pr-list
Availability: InStock
Author: yongwoon

Extract merged pull request numbers from commit headlines and update release PR descriptions.

8|1|Updated May 13, 2026

Search Tags:#automation #git #documentation #pull request #github #release

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-release-pr-list

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-release-pr-list
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-release-pr-list
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-release-pr-list

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3, bash, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the manual, error-prone task of compiling a list of merged pull requests for release notes, ensuring accurate attribution and audit trails for every release.

Core Features & Use Cases

Automated PR Extraction: Automatically identifies merged PRs from commit headlines within a release PR.
Author-Based Attribution: Groups PRs by author and sorts them alphabetically for clear, professional release documentation.
Interactive Summarization: Optionally generates concise, title-based summaries for each PR to provide context to stakeholders.

Quick Start

Use the ywc-release-pr-list skill to generate and update the PR list for release PR number 301.

Frequently Asked Questions about ywc-release-pr-list

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

FAQPage Schema

How do I automate release PR descriptions with merged pull request lists?▼

Automate release PR descriptions by extracting merged pull request numbers from commit headlines and updating the PR body with an author-grouped list, ensuring accurate attribution and audit trails for every release.

How does author-based attribution work for GitHub release notes?▼

Author-based attribution works by grouping extracted merged pull requests by their respective authors and sorting them alphabetically, generating clear and professional release documentation automatically.

Do I need GitHub CLI to extract merged pull requests from commit headlines?▼

Yes, you need GitHub CLI, along with Python3 and Bash, to extract merged pull request numbers from commit headlines and perform idempotent PR description updates.

Can I generate summaries for merged pull requests in a release PR?▼

Yes, you can optionally generate concise, title-based summaries for each merged pull request to provide additional context to stakeholders directly within the release PR description.

What is the best way to group pull requests by author for release management?▼

The best way to group pull requests by author is to automate the extraction of merged PR numbers from commit headlines and update the release PR description with an alphabetically sorted, author-grouped list.