doc-changelog

Generate user-facing changelog content from git history or CHANGELOG.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill doc-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-changelog
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/doc-changelog
Command: npx skills add https://github.com/Swear4/agent_rules --skill doc-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning technical release details into customer-friendly changelog content so users understand the value of new releases without wading through internal jargon.

Core Features & Use Cases

  • Automatic extraction: Derive user-facing changes from git history or CHANGELOG.md and translate them into customer-focused statements.
  • Cross-linking: Optionally connect each item to related documentation articles when available via features.json to provide deeper context.
  • Release-ready formatting: Produce a coherent, version-scoped changelog ready for publishing to KB or product docs.

Quick Start

Provide the latest release information in the required format to generate the user-facing changelog.

Frequently Asked Questions about doc-changelog

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

FAQPage Schema
How do I generate user-facing changelog content from git commit history?

To generate user-facing changelog content from git commit history, this Skill automatically extracts technical changes and translates them into customer-focused statements. It reads your git log to derive release-ready documentation.

What is the best way to turn technical release notes into customer benefits?

Turning technical release notes into customer benefits involves translating internal jargon into user-facing value. This Skill processes your commit history or CHANGELOG.md to produce customer-friendly changelog entries.

Can I cross-link changelog entries with documentation features?

Yes, you can cross-link changelog entries with documentation features. When a features.json file is available, the Skill optionally connects each generated changelog item to related documentation articles for deeper context.

Do I need a CHANGELOG.md file to generate release notes, or can I use git log?

You do not need a CHANGELOG.md file exclusively; you can use git log. The Skill requires either a git log or an existing CHANGELOG.md to extract technical changes and format them into user-facing release notes.

How does automatic changelog generation handle version scoping for product docs?

Automatic changelog generation handles version scoping by organizing extracted git commits into a coherent, version-scoped changelog. This produces release-ready formatting suitable for publishing directly to your knowledge base or product docs.

Can I enrich changelog entries using features.json?

Yes, you can enrich changelog entries using features.json. When available, the Skill reads this file to add deeper context and cross-link generated release notes with related documentation features.