docs-changelog

Generate release changelog markdown files from version, timestamp, and GitHub release notes.

17|2|Updated Mar 5, 2026

Search Tags:#changelog #versioning #documentation #release notes #release automation #markdown formatting #GitHub compare

Ready to run

npx skills add https://github.com/DavidLiuXh/jarvis-personal-ai --skill docs-changelog-davidliuxh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-changelog
Source: https://github.com/DavidLiuXh/jarvis-personal-ai/tree/main/.gemini/skills/docs-changelog
Command: npx skills add https://github.com/DavidLiuXh/jarvis-personal-ai --skill docs-changelog-davidliuxh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual effort and inconsistencies involved in preparing release notes and changelog markdown files for each new version.

Core Features & Use Cases

Automated changelog generation: Produces standardized updates for docs/changelogs pages based on a release version and raw “What’s Changed” content.
Version-path aware updates: Chooses the correct workflow for nightly, stable minor (ending in .0), stable patches, and preview releases, including special handling for preview vs latest.
Highlights formatting: Creates 3–5 feature-focused highlight bullets with a consistent style while filtering contributor sections and avoiding experimental language in stable highlights.
Full changelog link correction: Updates only the end version portion of the “Full Changelog” URL for patch releases.
Output consistency: Ensures the final files are formatted using the repository’s standard formatter command.

Quick Start

Ask Jarvis to run docs-changelog for version v0.28.1 with the release TIME and BODY from the upstream release notes.

Frequently Asked Questions about docs-changelog

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

FAQPage Schema

How do I generate release notes markdown from a raw GitHub release body?▼

To generate release notes markdown, the Skill parses your raw GitHub release body, removes contributor sections, normalizes pull request URLs into markdown, and formats the final changelog file using your repository's standard formatter command.

How do I format changelog highlights for different release types like stable patches and previews?▼

Formatting changelog highlights for stable patches and previews requires selecting the correct target template, prepending feature-focused bullets, and filtering out experimental language to ensure stable releases maintain a consistent style.

How do I update the Full Changelog compare URL for patch releases?▼

Updating the Full Changelog compare URL for patch releases involves rewriting only the end version portion of the GitHub compare link while skipping nightly versions to maintain accurate versioning paths.

Can I automate release documentation updates for minor versions and nightly builds?▼

Automating release documentation updates for minor versions and nightly builds is supported through version-path aware workflows that select the correct processing logic for stable minor releases ending in .0, patches, and previews.

Why does my changelog generation include contributor sections in the highlights?▼

Changelog generation includes contributor sections when the parsing logic fails to remove them; the Skill is designed to filter these sections out automatically while creating 3-5 feature-focused highlight bullets for your release notes.