Skills Guide

PR Changelog Generator

VerifiedSafe

Generates a changelog for a branch by analyzing commit messages and diffs. Produces a structured summary with a title, one-sentence motivation, and up to three key changes. Helps streamline PR descriptions and release notes.

Sby Skills Guide Bot
DevelopmentIntermediate
606/2/2026
Claude Code
#pr-summarize#changelog#git#pull-request

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Generates a concise changelog summary for the current branch from the Git diff.

Strengths

  • Automatically detects the repository's commit message convention
  • Produces a clear title and explanation
  • Limits 'How' bullets to three for conciseness

Limitations

  • Relies on default branch detection which may fail
  • Does not handle branches with many merged commits
When to use it

When you need to quickly create a changelog summary for a pull request.

When not to use it

For detailed code reviews requiring line-by-line analysis.

Security analysis

Safe
Quality score85/100

The skill only instructs to run read-only git commands (log, diff) to generate a summary, with no destructive or exfiltration actions.

No concerns found

Examples

Generate PR changelog
Generate a changelog for the current branch following the repo's commit convention.
Summarize branch changes
Summarize the changes on this branch in a concise PR changelog format.

name: dev-pr-summarize description: Generate a concise PR changelog summary from the current branch diff.

pr-summarize - PR Changelog Generator

Generate a clear, minimal changelog for the current branch.

Instructions

  1. Detect the default branch: BASE=$(git remote show upstream 2>/dev/null | sed -n 's/.*HEAD branch: //p') || BASE=main
  2. Run git log --oneline -10 $BASE to study the repo's commit message convention (e.g., feat:, MSSQL:, [COMPONENT], plain imperative, etc.)
  3. Run git log --oneline $BASE..HEAD to get commits on the branch
  4. Run git diff $BASE...HEAD --stat to see changed files
  5. Run git diff $BASE...HEAD to read the actual changes
  6. Produce a changelog using the template below, with the title matching the repo's convention
  7. If this is in main branch, create a new branch for this change

Template

## <Short imperative title describing the change>

## Why

<One sentence explaining the motivation or problem>

## How (at most 3 points, start with verb)

- <Bullet points describing what was done, keep each line short>
- <Focus on what changed, not implementation details>

Rules

  • Title must follow the repo's commit message convention detected in step 1
  • "Why" is one sentence max
  • "How" bullets should be extremely minimal and clear
  • No fluff, no over-explanation
  • Output only the changelog, nothing else
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin