skills.rest
viditparashar96
viditparashar96COMMUNITY
Explore all skills by this author →
GitHub

eng-release-notes

Convert git history and PR data into structured release notes.

Updated Apr 14, 2026
Search Tags:#automation#git#workflow#changelog#release#notes#pull-request
One-click install
npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-release-notes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eng-release-notes
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/eng-release-notes
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically transforms raw git history and PR data into clean, audience-appropriate release notes, saving teams hours of manual writing.

Core Features & Use Cases

  • Gather: determine scope, extract git history, fetch PR data when connected, and read PRODUCTS.md to map changes to features dynamically.
  • Categorize: apply ultrathink to classify changes into Breaking, Features, Bug Fixes, Performance, Security, Docs, Refactoring, and Deps.
  • Generate: locally create docs/releases/{version}.md with sections for highlights, features, bugs, performance, and contributors; tailor notes for internal or customer audiences.
  • Distribute: prepare GitHub releases and stakeholder emails, and log summaries to memory.

Quick Start

Run the release notes workflow to generate a versioned changelog from your git history.

Frequently Asked Questions about eng-release-notes

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

FAQPage Schema
How do I automate release notes from git history?▼

You can automate release notes by analyzing git commits and PR data to categorize changes into structured sections like features, bug fixes, and security. The tool generates a versioned markdown changelog locally in your docs folder.

Can I generate a changelog categorized for different audiences from pull requests?▼

Yes, changelog generation tailors release notes for internal or customer audiences by analyzing pull request data and commit history. It dynamically maps changes to features using a PRODUCTS.md file.

What's the best way to format git commits into structured release categories?▼

The best way to format commits into structured release categories is using an automated workflow that classifies changes into Breaking, Features, Bug Fixes, Performance, Security, Docs, Refactoring, and Deps.

Does this release notes workflow support publishing to GitHub releases?▼

Yes, the release notes workflow supports distributing generated changelogs via GitHub releases. It also prepares stakeholder emails and logs summaries to memory after creating the local markdown file.

Do I need a PRODUCTS.md file to map git changes to features?▼

A PRODUCTS.md file is used to dynamically map git changes to features during the release notes generation process. Reading this file helps categorize commits accurately for the final versioned markdown output.

Related Skills

Explore More Software Engineering Skills→
mgd34msumgd34msu
4

git-workflows

Generate pull request descriptions, commit messages, and release notes for Git workflows.

Community
Intermediate
frostantfrostant
42

changelog-generator

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

Community
Intermediate
DonTiziDonTizi
2

release

Automate Python project releases with version bumps, changelog updates, and Git tags.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-changelog

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

Community
Intermediate