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.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#pr-summarize#changelog#git#pull-request

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

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

How this analysis is made

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/pr-changelog-generator-mm5t8cas' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pr-changelog-generator-mm5t8cas/download' --output '.skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md.part' && mv '.skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md.part' '.skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md' && test -s '.skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dev-pr-summarize' && cp -R '.skill-downloads/pr-changelog-generator-mm5t8cas' '.claude/skills/dev-pr-summarize'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/pr-changelog-generator-mm5t8cas'

openskills read 'pr-changelog-generator-mm5t8cas'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/pr-changelog-generator-mm5t8cas/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot