rocha-changelog

Generate Markdown changelogs from merged GitHub PRs via gh CLI.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/renato0307/rocha --skill rocha-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rocha-changelog
Source: https://github.com/renato0307/rocha/tree/main/.claude/skills/rocha-changelog
Command: npx skills add https://github.com/renato0307/rocha --skill rocha-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of release notes by summarizing PRs merged into the main branch, saving teams from manual drafting.

Core Features & Use Cases

  • Auto-aggregates merged PRs: Collects PRs merged to main within the target time window and groups changes by type.
  • Changelog structure: Produces sections for Breaking Changes, New Features, Bug Fixes, Improvements, and Documentation.
  • Contributor attribution: Credits PR authors and contributors for each entry.
  • Release-ready output: Outputs a clean Markdown changelog suitable for release notes and internal docs.

Quick Start

Use the rocha-changelog skill to generate a changelog for PRs merged into main in the selected time window (daily, weekly, or N days). For example, ask: "Generate a daily changelog for PRs merged to main in the last 24 hours."

Frequently Asked Questions about rocha-changelog

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

FAQPage Schema
How do I generate a changelog from merged PRs in GitHub?

You can generate a changelog from merged PRs by querying GitHub via the gh CLI over a selected time window, categorizing changes by type, and crediting contributors. This produces a structured Markdown document suitable for release notes.

What is the best way to automate release notes from GitHub PRs?

Automating release notes from GitHub PRs involves aggregating merged PRs within a target time window and grouping changes into sections like Breaking Changes, New Features, and Bug Fixes. This outputs a Markdown changelog crediting PR authors and contributors.

Does the changelog generation process require the gh CLI?

Yes, the changelog generation process requires the gh CLI to query GitHub, parse PR metadata, and extract labels. It uses the command-line interface to fetch pull request data for building the release-ready Markdown output.

Can I generate a daily or weekly changelog for PRs merged to main?

Yes, you can generate a daily or weekly changelog for PRs merged to main by specifying a custom time window. The process analyzes PRs merged over that period, categorizes changes, and credits contributors in the final Markdown output.

What sections are included in an automated Markdown changelog?

An automated Markdown changelog includes sections for Breaking Changes, New Features, Bug Fixes, Improvements, and Documentation. These sections are populated by parsing PR metadata and labels from merged pull requests.

How do I credit contributors in automated release notes?

To credit contributors in automated release notes, the changelog generation process parses PR metadata to identify and attribute PR authors and contributors for each entry. This ensures all participants are recognized in the Markdown output.