skillshare-changelog

Generate CHANGELOG.md entries from commits between tags and sync website changelog.

302|22|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/JetBrains/skills --skill skillshare-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillshare-changelog
Source: https://github.com/JetBrains/skills/tree/main/changelog
Command: npx skills add https://github.com/JetBrains/skills --skill skillshare-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual release-note creation is time-consuming and error-prone. This skill automates generating CHANGELOG.md entries from recent commits (using conventional commits) and keeps the website changelog in sync, reducing manual effort and mistakes.

Core Features & Use Cases

  • Generate a CHANGELOG.md entry for a release by scanning commits between tags.
  • Sync the website changelog page to reflect the latest release notes.
  • Apply to multi-repository release workflows to maintain consistent user-facing documentation.

Quick Start

Generate a changelog for the latest release tag.

Frequently Asked Questions about skillshare-changelog

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

FAQPage Schema
How do I auto-generate release notes from conventional commits?

You can auto-generate release notes by scanning commits between the latest and previous Git tags. This skill formats conventional commits into user-facing entries and updates your CHANGELOG.md automatically.

How do I keep my website changelog in sync with my repository tags?

To keep your website changelog in sync, this skill reads recent Git tags, formats the release notes, and applies the updates directly to both CHANGELOG.md and the website changelog page.

Can I apply automated changelog generation across multiple repositories?

Yes, you can apply automated changelog generation across multiple repositories. The skill integrates into multi-repository release workflows to maintain consistent user-facing documentation.

What is the best way to format changelog entries from recent Git commits?

The best way to format changelog entries is using the conventional commits standard. This skill parses commit history between tags to structure user-facing release notes accurately.

Does this changelog automation require specific dependencies or components?

No specific dependencies or components are required to run this changelog automation. It operates independently to read Git tags and generate formatted documentation.