skills.rest
djscrew1738
djscrew1738COMMUNITY
Explore all skills by this author →
GitHub

release-notes

Generate a structured markdown changelog from git history since the latest release tag.

Updated Jan 14, 2026
Search Tags:#git#changelog#version control#release notes#automated documentation
One-click install
npx skills add https://github.com/djscrew1738/plumbprice --skill release-notes-djscrew1738
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/djscrew1738/plumbprice/tree/main/.agents/skills/release-notes
Command: npx skills add https://github.com/djscrew1738/plumbprice --skill release-notes-djscrew1738

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of formatted changelogs from git history, simplifying the process of preparing release notes for software updates.

Core Features & Use Cases

  • Git History Analysis: Analyze git history since the last release tag.
  • Categorization of Changes: Organize changes into sections such as Breaking Changes, Added, Changed, Fixed, and Notes.
  • User-Facing Changes: Focus on changes relevant to users, including features, important bug fixes, and breaking changes.
  • Markdown Output: Provide a changelog in markdown format, ready for copying into GitHub releases.

Quick Start

Use the release-notes skill to generate a changelog by typing: /release-notes

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate a changelog from git history for my release notes?▼

You can generate a changelog from git history by analyzing commits and merged PRs since the latest release tag, organizing changes into categorized markdown release notes for your software updates.

What is the best way to automate user-facing release notes from version control?▼

The best way to automate user-facing release notes is by parsing git history to identify features, bug fixes, and breaking changes, then categorizing them into a structured changelog format for software updates.

Does this automated documentation tool require specific git knowledge to use?▼

Yes, generating automated documentation requires basic knowledge of git and command-line operations to identify release tags and compare commits for structured changelogs.

How are categorized changes structured in the generated markdown output?▼

Changes in the markdown output are organized into specific sections including Breaking Changes, Added, Changed, Fixed, and Notes, focusing on user-facing software updates.

Can I use this to prepare formatted changelogs directly for GitHub releases?▼

Yes, you can prepare formatted changelogs for GitHub releases because the Skill outputs markdown directly from git history, making it ready to copy into your version control release notes.

Related Skills

Explore More Software Engineering Skills→
FutureAtomsFutureAtoms
1

git-github-changelog

Generate and update changelogs in Keep a Changelog format from Git commit history.

Community
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
darblexdarblex

git-essentials

Provide essential Git commands for version control, branching, and collaboration.

Community
Intermediate
sobhanashinesobhanashine
1

ship

Automate software deployment by merging branches, running tests, and updating versioning.

Community
Advanced