changelog

Keep CHANGES.md release notes in sync with code changes.

10.2k|811|Updated Mar 9, 2011
One-click install
npx skills add https://github.com/JetBrains/ideavim --skill changelog-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/JetBrains/ideavim/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/JetBrains/ideavim --skill changelog-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains the IdeaVim changelog (CHANGES.md) in sync with code changes across releases, ensuring accurate release notes and a clear historical record.

Core Features & Use Cases

  • Coordinate changelog entries with commits and PRs to reflect new features, fixes, and changes.
  • Preserve the historical gap note between versions 2.9.0 and 2.28.0 in the CHANGES.md as required.
  • Review and structure release notes for upcoming versions before publishing.

Quick Start

Add a new changelog entry under the [To Be Released] section for the upcoming release with references to relevant commits and PRs.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I keep CHANGES.md release notes in sync with code changes?

Synchronizing CHANGES.md release notes involves adding new changelog entries under the [To Be Released] section for the upcoming release, ensuring entries coordinate with relevant commits and PRs.

What is the process for adding changelog entries during release preparation?

The changelog process for release preparation involves structuring release notes for upcoming versions by adding entries under the [To Be Released] section while linking them to related commits and PRs before publishing.

How do I preserve the historical gap note between versions 2.9.0 and 2.28.0 in the changelog?

To preserve the historical gap note between versions 2.9.0 and 2.28.0, you must follow the documented changelog rules that require retaining this specific note in CHANGES.md during ongoing maintenance.

Can I use this changelog process for PR reviews?

Yes, the changelog maintenance process applies to PR reviews by coordinating changelog entries with commits and pull requests to accurately reflect new features, fixes, and changes across versions.

Are there limitations when maintaining the IdeaVim changelog across multiple versions?

A key constraint is the requirement to preserve the historical gap note between versions 2.9.0 and 2.28.0 in CHANGES.md, which must be maintained without alteration during ongoing changelog maintenance.