mcp-vkusvill: Skill for Claude Code

CHANGELOG Generator

Generate a new CHANGELOG.md entry covering changes between the last version recorded in CHANGELOG.md and either the current package.json version or an explicitly-specified TO version. Only substantial changes are included; cosmetic/style/internal-tooling churn is filtered out.

The CHANGELOG.md lives at the repo root and follows the Keep a Changelog format with sections Breaking / Added / Changed / Deprecated / Removed / Fixed / Security. Breaking is project-specific and takes precedence; the rest match Keep a Changelog verbatim.

Argument Parsing

$ARGUMENTS is optional. If supplied, the first token must be a semver string X.Y.Z and is treated as the TO version. Anything that doesn't match ^\d+\.\d+\.\d+$ is ignored.

Args	FROM-VER	TO-VER
none	latest version in CHANGELOG.md	package.json version field
one X.Y.Z	latest version in CHANGELOG.md	X.Y.Z

Workflow

Step 1: Resolve FROM-VER from CHANGELOG.md

Read CHANGELOG.md at repo root. Find all version headings matching the regex:

^##\s+\[?(\d+\.\d+\.\d+)\]?

The first match (top-most in the file) is the latest version recorded.

Step 2: Resolve TO-VER

• If $ARGUMENTS contains a X.Y.Z token: TO-VER = that token.
• Otherwise: read package.json version field via node -e "console.log(require('./package.json').version)".

If FROM-VER == TO-VER, stop with No new version to record — CHANGELOG.md is up to date with v<VER>.

Step 3: Resolve commit hashes for FROM-VER and TO-VER

For each version, find the commit that bumped the project to it. The convention is that version-bump commits have the version string as the entire commit subject (e.g. subject 1.2.3).

git log --format="%H %s" | awk -v v="<VER>" '$2 == v { print $1; exit }'

Fallback if the above returns nothing — find the first commit where package.json version was set to that value: