skills.rest
v1-io
v1-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

changelog

Generate markdown changelog entries from merged GitHub PRs.

6|2|Updated Jan 15, 2026
Search Tags:#changelog#documentation#release-notes#github-api#pr-automation
One-click install
npx skills add https://github.com/v1-io/v1tamins --skill changelog-v1-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/v1-io/v1tamins/tree/main/claude/skills/changelog
Command: npx skills add https://github.com/v1-io/v1tamins --skill changelog-v1-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of release notes by aggregating merged PRs since the last changelog, reducing manual toil and aligning teams on new changes.

Core Features & Use Cases

  • Detects the latest changelog file and reads its date to establish the window for new PRs.
  • Fetches merged PRs from the repository since that date and extracts titles, descriptions, and metadata.
  • Generates a new markdown changelog entry formatted for standard release notes and teams, including a summary of major changes and minor updates.
  • Use Case: A product team publishes a biweekly release notes document by running the tool to convert recent PR activity into a readable changelog.

Quick Start

Run the changelog workflow to generate a new release notes entry from merged PRs since the last changelog.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate release notes from merged pull requests?▼

You can automatically generate release notes by aggregating merged pull requests since the last changelog date, fetching PR titles and metadata via the GitHub API, and formatting them into a new markdown changelog entry.

How does the changelog generation process determine which pull requests to include?▼

The changelog generation process detects the latest changelog file, reads its date to establish a time window, and then fetches all pull requests merged via the GitHub API since that specific date.

Can I customize the output directory and formatting for my project's release notes?▼

Yes, you can configure changelog directories and formatting to meet your project conventions, ensuring the generated release notes align with your team's standard documentation structure and markdown styling.

Does this release notes automation work across multiple GitHub repositories?▼

Yes, the release notes automation applies to software teams managing public or internal changelogs across GitHub repositories and multiple projects, handling varying PR formats from different sources.

What do I need to set up before generating changelog entries from GitHub PRs?▼

You need to provide access to your repository's pull request data via the GitHub API and have an existing changelog file in your configured directory to establish the starting date for fetching merged PRs.

Related Skills

Explore More Content & Communication Skills→
Luohao-YanLuohao-Yan
6

changelog-draft

Generate changelog drafts from merged PRs with markdown and JSON outputs.

Community
Advanced
omeragaakbasomeragaakbas

stakeholder-map

Generate a stakeholder map and communication plan table from project briefs.

Community
Intermediate
getsentrygetsentry
905

pr-writer

Standardize GitHub pull request titles, descriptions, and issue references with Sentry conventions.

Official
Advanced
SfzmangoSfzmango
1

release-notes

Compile release notes from git commit ranges and merged pull requests.

Community
Advanced