skills.rest
sahilrajput280
sahilrajput280COMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate standardized changelog files from PR commits against main.

Updated Aug 23, 2026
Search Tags:#automation#git#changelog#documentation#pr#release-notes#commit-scan
One-click install
npx skills add https://github.com/sahilrajput280/DOGRAH --skill changelog-sahilrajput280
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/sahilrajput280/DOGRAH/tree/main/pipecat/.claude/skills/changelog
Command: npx skills add https://github.com/sahilrajput280/DOGRAH --skill changelog-sahilrajput280

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating changelog entries for PRs is tedious and error-prone; this skill automates generating standardized changelog files from PR commits.

Core Features & Use Cases

  • Automated changelog generation: scans commits on the PR against main and creates concise entries.
  • Standardized formatting: writes entries to the changelog/ folder using the {PR_NUMBER}.<type>.md naming convention with allowed types such as added, changed, fixed, and others.
  • Selective changes: skips non-user-facing or documentation-only changes according to policy.
  • Use Case: prepare release notes for a PR or generate changelog entries for a feature branch before merging.

Quick Start

Run this skill with the PR number to generate changelog entries in the changelog/ folder.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate changelog entries from git commits for a PR?▼

Automatically generate changelog entries by scanning commits on your PR branch against main. The skill summarizes the commits and writes standardized entries directly to the changelog folder.

What is the standard format for PR changelog files when automating release notes?▼

Standardized changelog files use a {PR_NUMBER}.<type>.md naming convention. Allowed types include added, changed, and fixed, ensuring consistent release notes formatting across your project.

Can I skip non-user-facing or documentation-only changes in automated changelog generation?▼

You can skip non-user-facing and documentation-only changes during automated changelog generation. The skill applies policy rules to filter commits, ensuring only user-facing changes are written.

How do I prepare release notes for a feature branch before merging?▼

Generate release notes for a feature branch by running the skill with your PR number. It scans branch commits against main and creates concise changelog entries for the upcoming merge.

Do I need any specific dependencies to automate PR changelog creation?▼

You do not need any specific dependencies to automate PR changelog creation. The skill operates independently to scan git commits and write standardized markdown entries to the changelog directory.

When should I not use automated commit scanning for changelog generation?▼

Automated commit scanning for changelog generation is not suitable for non-user-facing changes. The skill skips documentation-only updates according to policy, focusing on user-facing entries.

Related Skills

Explore More Software Engineering Skills→
styrene-labstyrene-lab
47

git

Standardize git workflow metadata across commits, branches, tags, and changelogs.

Official
Intermediate
meirmmeirm
13

writing-release-notes

Generate categorized markdown release notes from git history and version files.

Community
Advanced
stablyaistablyai
40.6k

review-and-submit

Reviews code changes, fixes issues in two rounds, then creates and merges a PR.

Official
Advanced
oldwinteroldwinter
5

changelog-generator

Generates formatted changelogs from git commit history for each release.

Community
Intermediate