# Maintain Accurate IdeaVim Changelogs

Release notes become inconsistent when commits, tickets, and user impact are reviewed separately. This skill turns repository history into organized, user-focused IdeaVim changelog entries.

## Install

```bash
npx skillstore add jetbrains/changelog
```

## Metadata

- Status: approved
- Slug: jetbrains-changelog
- Skillstore revision: r3
- Version status: missing
- Tree hash: 9675a97e9b189f0eb722c9afcfbcb9074454848b46f50a9e362d723c2fc083ec
- Author: JetBrains
- GitHub username: JetBrains
- License: MIT
- Repository: https://github.com/JetBrains/ideavim/tree/master/.claude/skills/changelog/
- Ref: 1c2ebded2116f8124f45dba86a2e567f56e64d8e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/jetbrains-changelog
- Manifest: https://skillstore.pages.dev/api/skills/jetbrains-changelog/manifest

## Capabilities

- Reviews the top portion of CHANGES.md and identifies the current unreleased section.
- Inspects commits, tags, pull requests, and selected file changes for user-visible updates.
- Groups entries into features, fixes, changes, and merged pull requests.
- Preserves IdeaVim heading, ordering, linking, and historical-gap conventions.
- Writes concise changelog descriptions with relevant issue and pull request references.

## Use Cases

- Prepare Release Notes: Review changes since the last release and organize them into a clean, user-facing changelog draft.
- Document Merged Work: Identify important features and fixes from commits and pull requests, then add accurate issue references.
- Review a Changelog Update: Check an existing draft for duplicate entries, incorrect sections, missing context, and formatting problems.

## Prompt Templates

### Draft the Unreleased Section

```
Review the current repository changes and draft concise entries for the To Be Released section of CHANGES.md.
```

### Summarize a Release

```
Review commits since the previous version, identify user-visible changes, and group them into Features, Fixes, and Changes.
```

### Audit Existing Entries

```
Review the current changelog draft for duplicates, vague descriptions, incorrect ticket placement, and violations of the IdeaVim format.
```

### Reconcile History and Pull Requests

```
Compare tags, commits, merged pull requests, tests, and recent changelog updates. Produce a release-ready draft and explain each inclusion or exclusion.
```

## Limitations

- It cannot determine user impact when repository changes or tests lack sufficient detail.
- It depends on available Git, GitHub CLI, repository, and network access.
- It does not validate the final changelog against every project build or release rule.
- It should not publish changes or create pull requests without explicit user approval.

## Best Practices

- Describe visible behavior and user impact instead of internal implementation details.
- Review tests and actual file changes before writing a specific entry.
- Preserve the existing structure, newest-first order, and exact release headings.

## Anti Patterns

- Do not invent issue numbers, release dates, or behavior not supported by repository evidence.
- Do not duplicate one change across multiple changelog sections.
- Do not edit build configuration or create a pull request without explicit approval.

## Security Audit

- Audited at: 2026-08-07T09:58:30.181\+00:00
- Summary: All 54 static findings are false positives. The detected backticks are Markdown examples or command references, the URLs are documentation links, and the reconnaissance matches are ordinary editorial guidance; no prompt injection or malicious intent was found in SKILL.md.

## Stats

- Views: 282
- Downloads: 8
- Favorites: 0
- Popularity score: 0