skills.rest
xriu
xriuCOMMUNITY
Explore all skills by this author →
GitHub

pr-brief

Generates a concise pull request changelog from commits grouped by conventional commit type.

2|2|Updated Dec 23, 2017
Search Tags:#git#changelog#pull request#conventional commits#pr summary#commit grouping
One-click install
npx skills add https://github.com/xriu/dotfiles --skill pr-brief-xriu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-brief
Source: https://github.com/xriu/dotfiles/tree/main/home/.skills/pr-brief
Command: npx skills add https://github.com/xriu/dotfiles --skill pr-brief-xriu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing pull request descriptions by hand is repetitive and often skipped, leaving reviewers without context. This Skill turns the commits between your branch and main into a structured, categorized changelog automatically. ## Core Features & Use Cases - Commit Grouping: Categorizes commits by conventional commit prefixes such as feat, fix, refactor, chore, docs, perf, test, and style. - Standardized Template: Produces a consistent Markdown changelog with mandatory category icons and bullet-point change descriptions. - Use Case: Before opening a pull request, ask for a quick PR summary and receive a ready-to-paste changelog with features, fixes, and chores grouped and linked to issue references. ## Quick Start Ask the assistant to generate a concise PR changelog summarizing the commits on the current branch compared to main.

Frequently Asked Questions about pr-brief

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

FAQPage Schema
How do I generate a pull request summary from git commits?▼

Run git log --oneline main..HEAD to list commits on your branch, then group them by conventional commit prefix such as feat or fix. This Skill automates that process and outputs a formatted Markdown changelog with category icons.

How to group commits by conventional commit type for a changelog?▼

Map each commit prefix to a category: feat becomes Features, fix becomes Fixes, refactor becomes Refactoring, and chore becomes Chores. Merge commits are skipped so only meaningful changes appear in the changelog.

Does this PR summary include test results or verification metrics?▼

No, this Skill produces a lightweight changelog only. It is designed for quick PR descriptions without verification steps, metrics, or CI results, making it unsuitable when full review evidence is required.

What base branch does the PR changelog compare against?▼

By default it compares the current branch against main using git log main..head. You can substitute any appropriate base branch if your repository uses a different default such as develop or master.

When should I not use a concise PR changelog?▼

Avoid it when reviewers need verification evidence, test coverage data, or detailed migration notes. The concise format intentionally omits metrics and deep context, so use a full PR template for high-risk changes.

Related Skills

Explore More Software Engineering Skills→
michael-conradmichael-conrad

changelog-generator

Generates categorized changelogs and release notes from git commit histories.

Community
Intermediate
liatrio-labsliatrio-labs
2

create-pull-request

Generate pull request titles and descriptions from git branch changes.

Official
Advanced
ceedaragentsceedaragents
794

verify-and-ship

Runs tests, lint, and type checks, updates changelogs, and creates pull requests or merge requests.

Official
Advanced
BrightBlockBrightBlock
2

describe_pr_nt

Generate PR descriptions from a built-in template using PR metadata.

Official
Advanced