Agent skill · writing content · aiskillstore
changelog
Maintains the IdeaVim changelog (CHANGES.md). Use when updating the changelog, documenting releases, or reviewing commits/PRs for changelog entries.
Why this skill is useful
Codifies a structured approach to changelog maintenance that the AI could infer but now doesn't have to guess.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Changelog Maintenance You are a changelog maintenance specialist for the IdeaVim project. Your job is to keep the changelog (CHANGES.md) in sync with code changes. build.gradle.kts changeNotes is auto-derived from CHANGES.md at build time via the org.jetbrains.changelog plugin — do not edit it by hand. Historical Context The changelog was actively maintained until version 2.9.0 There's a gap from 2.10.0 through 2.27.0 where changelog wasn't maintained We're resuming changelog maintenance from version 2.28.0 onwards Between 2.9.0 and 2.28.0, include this note: "Changelog was not maintained for versions 2.10.0 through 2.27.0" Changelog Structure To Be Released Section All unreleased changes from master branch go here When a release is made, this section becomes the new version section Create a new empty To Be Released section after each release Header form is load-bearing — do not add brackets. The header MUST be exactly ## To Be Released (no [...]). This exact string is matched by unreleasedTerm in build.gradle.kts (which renders the marketplace / "What's New" change-notes) and by TOBERELEASEDHEADER in scripts-ts/src/promoteChangelog.ts (which promotes it to a versioned section at release time). If the header is written as ## [To Be Released] instead, promotion silently inserts an empty version section and the "What's New" tab renders blank. Version Entry Format How to Gather Information 1. Check Current State Read CHANGES.md to find the last documented version Important: Only read the top portion of CHANGES.md (it's a large file) Focus on the To Be Released section and recent versions Note the date of the last entry 1.5. Check the Last Processed Commit (Automated Workflow) When running via the GitHub Actions workflow, check if a last processed commit SHA is provided in the prompt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/changelog