release-changelog

Generate structured Markdown changelogs from git history, changesets, and merged pull requests.

Updated May 27, 2026

Search Tags:#automation #git #changelog #versioning #documentation #release

Ready to run

npx skills add https://github.com/bychrisr/now-company --skill release-changelog-bychrisr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/bychrisr/now-company/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/bychrisr/now-company --skill release-changelog-bychrisr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual effort and human error involved in tracking commits, PRs, and changesets to compile accurate, user-facing release notes for stable software versions.

Core Features & Use Cases

Automated Changelog Generation: Aggregates git history, changesets, and merged PRs into a standardized Markdown format.
Breaking Change Detection: Automatically scans for destructive migrations and API changes to ensure upgrade paths are documented.
Contributor Attribution: Identifies and lists contributors from merge commit history while excluding bots and internal maintainers.

Quick Start

Ask the agent to generate the stable release changelog for the current repository state based on the latest git tag.

Frequently Asked Questions about release-changelog

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

FAQPage Schema

How do I generate a changelog for a stable software release from git history?▼

To generate a changelog for a stable software release, this skill aggregates git commits, changeset files, and merged pull requests into a standardized Markdown format. It identifies breaking changes, feature highlights, and contributors automatically.

How does automated changelog generation detect breaking changes?▼

Automated changelog generation detects breaking changes by scanning git history and pull requests for destructive migrations and API changes. This ensures upgrade paths are properly documented in the final release notes.

Do I need the GitHub CLI to generate release notes from merged pull requests?▼

Yes, you need the GitHub CLI to generate release notes from merged pull requests, as the skill requires it to fetch PR metadata. You also need local filesystem access to write the final release artifact.

Can I automatically list contributors in a markdown changelog while excluding bots?▼

You can automatically list contributors in a markdown changelog by identifying them from merge commit history. The skill specifically excludes bots and internal maintainers from the final attribution list.

What is the best way to maintain documentation for calendar-versioned projects?▼

The best way to maintain documentation for calendar-versioned projects is using an automated changelog generator that analyzes git tags and PRs. This creates structured, user-facing release notes aligned with your versioning scheme.