Claude Code Changelog Skill for IdeaVim Release Notes
Write IdeaVim release notes from actual code and test changes. Place user-facing features, fixes, and breaking changes in the unreleased section of CHANGES.md.
中文Install in Claude Code
Use Claude Code in the pinned IdeaVim repository. Have the relevant PR, any known YouTrack issue, and its tests available.
- Confirm `.claude/skills/changelog/SKILL.md` and `CHANGES.md` in the pinned IdeaVim checkout.
- Start Claude Code from the checkout root and call `/changelog` with the PR or commit range to inspect.
Example task
Suppose a practice change preserves selection after switching editor splits. Ask the skill to confirm the trigger in the new test and add one fix to the unreleased section. Omit an issue number because the exercise has no real ticket.What to check
Expect one fix entry under `## To Be Released` that describes the observed behavior. The project's build logic still derives the release notes from CHANGES.md.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why does IdeaVim require the exact `## To Be Released` heading?
The promotion script matches that heading when moving unreleased changes into a version section. A bracketed heading may prevent it from finding the section.