changelog
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "changelog" from https://skillstore.io/skills/jetbrains-changelog.md and its manifest at https://skillstore.io/api/skills/jetbrains-changelog/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "changelog". Review the latest changes and draft the unreleased changelog entries.
Expected outcome:
- ### Features: Added support for the gn text object and Next Edit Suggestion integration.
- ### Fixes: Fixed ci" behavior in empty strings and cursor positioning after undo.
Using "changelog". Check this release draft for quality and repository conventions.
Expected outcome:
- Moved the ticket link before the fix description.
- Removed a duplicate entry and clarified the affected Vim command.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (37)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/jetbrains-changelog/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/jetbrains-changelog?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/jetbrains-changelog?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jetbrains-changelog/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/jetbrains-changelog.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
JetBrains. (2026). changelog security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jetbrains-changelog/audits/9BibTeX citation
@techreport{jetbrains-jetbrains-changelog-2026,
author = {JetBrains},
title = {changelog security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/jetbrains-changelog/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "changelog security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "JetBrains"
date-released: "2026-08-07"
url: "https://skillstore.io/skills/jetbrains-changelog/audits/9"
identifiers:
- type: other
value: "skillstore:jetbrains-changelog:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Review the current repository changes and draft concise entries for the To Be Released section of CHANGES.md.
Review commits since the previous version, identify user-visible changes, and group them into Features, Fixes, and Changes.
Review the current changelog draft for duplicates, vague descriptions, incorrect ticket placement, and violations of the IdeaVim format.
Compare tags, commits, merged pull requests, tests, and recent changelog updates. Produce a release-ready draft and explain each inclusion or exclusion.
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.
Avoid
- 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.