Changelog

⚠️ IMPORTANT - READ FIRST

This skill ONLY updates CHANGELOG.md. The changelog file IS the canvas — always write the draft into it. Never dump the proposed entry into the chat.

• DO write the new version entry directly into the project's CHANGELOG.md and open it for review
• DO ask any clarifying questions first (version, which plugin, how to categorize an ambiguous change) — but the answer always lands in the file, not the chat
• DO NOT paste the full proposed changelog into the chat instead of writing it to the file
• DO NOT trigger any GitHub release workflows
• DO NOT run any other skills or workflows automatically
• DO NOT make any commits

Releases are handled by each repo's GitHub Actions release workflow. Your job ends once CHANGELOG.md is updated. After the user merges the changelog change, suggest they run the release workflow via gh workflow run (or via the Actions UI) — but never trigger it yourself.

Input

Project path (or run from project root)

Step 1: Identify Current State