skills.rest
jtangir87
jtangir87COMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate release changelogs from commit history and pull requests.

Updated Apr 3, 2026
Search Tags:#automation#git#changelog#versioning#release notes#pr
One-click install
npx skills add https://github.com/jtangir87/paperclip --skill release-changelog-jtangir87
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/jtangir87/paperclip/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/jtangir87/paperclip --skill release-changelog-jtangir87

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating detailed, user-friendly changelogs for software releases, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Changelog Generation: Reads commit history, pull requests, and changesets since a specified last stable release to assemble a comprehensive changelog.
  • Version Control: Adheres to calendar versioning and release conventions to produce accurate versioned changelog files.
  • Use Case: Developers use this Skill to automatically compile release notes before publishing a new version, saving hours of manual editing and error-prone reporting.

Quick Start

Generate the release notes by analyzing the latest commits and PRs since the previous stable tag, then review and finalize the changelog.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I automatically generate release notes from git commit history?▼

You can automatically generate release notes by analyzing your git commit history and pull requests since a specified stable release tag. This process compiles commit details and PR changesets to assemble a comprehensive changelog.

What is the best way to compile a changelog before publishing a new version?▼

The best way to compile a changelog is to automate the extraction of updates from commit history and pull requests. This ensures versioning standards are met and contribution attributions are included without manual effort.

Can I use pull request data to build versioned changelog files?▼

Yes, pull request data is analyzed alongside commit history to build versioned changelog files. The generated changelog adheres to calendar versioning and release conventions for accurate documentation.

Does this changelog generation approach work without external dependencies?▼

Yes, this changelog generation approach works without external dependencies. It internally analyzes your commit history and pull requests to produce detailed release notes independently.

When do I need to use an automated changelog generator in my development workflow?▼

You need an automated changelog generator when preparing to publish a new software version. It streamlines documentation by reducing manual editing and preventing reporting errors in your release notes.

Related Skills

Explore More Software Engineering Skills→
k97k97
4

gen-release-notes

Generate structured release notes from git commit history and pull request data.

Community
Advanced
vekzz-devvekzz-dev
3

changelog-maintenance

Standardize release documentation with semantic versioning and Keep a Changelog.

Community
Intermediate
k3nnethfrancisk3nnethfrancis
30

git-tracking

Bundle related changes into descriptive Git commits.

Community
Basic
nvimcraftnvimcraft

git-release

Generate release version recommendations and changelog drafts from Git history.

Community
Advanced