skills.rest
wopal-cn
wopal-cnOFFICIAL
Explore all skills by this author →
GitHub

cnb-pr-summary

Analyzes pull request diffs and generates structured change summaries grouped by module.

3|1|Updated Feb 26, 2026
Search Tags:#git#diff analysis#changelog#code review#pull request#merge request#change summary
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill cnb-pr-summary-wopal-cn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cnb-pr-summary
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/cnb-pr-summary
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill cnb-pr-summary-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing large pull requests is time-consuming, and manually writing change summaries often leads to missed breaking changes or unclear release notes. This Skill automates PR change analysis and produces concise, structured summaries. ## Core Features & Use Cases - Diff-Based Analysis: Retrieves PR change statistics, file lists, and key diffs via the cnb-pr-diff Skill, then filters out lock files, build artifacts, and generated files to focus on core code. - Structured Summary Output: Classifies changes by type (feat, fix, refactor, perf, docs, chore), groups them by module, and highlights breaking changes and risks. - Large PR Handling: For PRs with more than 20 files, it analyzes change distribution first, prioritizes core modules, and summarizes the rest. - Use Case: Before merging a feature branch, ask for a PR summary to get a one-line type description, per-module change list, and any compatibility risks for the merge request description. ## Quick Start Summarize the changes in this pull request and generate a structured change description highlighting any breaking changes.

Frequently Asked Questions about cnb-pr-summary

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

FAQPage Schema
How do I generate a summary of pull request changes?▼

Invoke the Skill on a pull request and it retrieves the diff statistics and file list, filters non-core files, then analyzes key changes. The output is a structured summary with change type, per-module modifications, and any breaking changes.

What files are excluded from PR change analysis?▼

The analysis skips dependency lock files like package-lock.json and go.sum, build outputs like dist/ and .next/, generated files like *.min.js and *.map, and pure test files unless tests are the focus of the change.

How are large pull requests with many files handled?▼

For PRs with more than 20 files, the Skill first analyzes change distribution with diff statistics, groups files by module, and prioritizes core modules with large or critical changes. Remaining files are summarized briefly at the end.

Does the PR summary identify breaking changes?▼

Yes, the analysis explicitly checks for incompatible changes, API modifications, and data structure changes that require migration. These are flagged in a dedicated note section of the output when present.

What is the output format of the PR change summary?▼

The output is a Markdown block with a one-line typed description (feat, fix, refactor, etc.), a bulleted list of changes grouped by module, and an optional note covering breaking changes or risks.

Related Skills

Explore More Software Engineering Skills→
horizontalsystemshorizontalsystems

aif-review

Review staged changes or pull requests for correctness, security, and maintainability issues.

Official
Advanced
abretonc7sabretonc7s

pr-changelog

Analyze pull request diffs to generate user-facing changelog entries.

Community
Basic
ourchitectureourchitecture
1

review-code

Automate code review of changed files for quality, security, and compliance issues.

Official
Advanced
stacklokstacklok
2.0k

commit-message

Generates commit messages from staged files for common use cases.

Official
Intermediate