From mattyp-changelog
Validates the changelog configuration file, checks required environment variables, template paths, and output writability, providing actionable fixes for failures.
How this command is triggered — by the user, by Claude, or both
Slash command
/mattyp-changelog:changelog-validateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /changelog-validate Validate `.changelog-config.json` before generating a changelog. ## Checks - Config exists and is valid JSON - Required environment variables exist (e.g., `GITHUB_TOKEN`, optional `SLACK_TOKEN`) - Template path exists - Output path is writable If validation fails, show actionable fixes (missing token env vars, missing template, invalid paths).
Validate .changelog-config.json before generating a changelog.
GITHUB_TOKEN, optional SLACK_TOKEN)If validation fails, show actionable fixes (missing token env vars, missing template, invalid paths).
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin mattyp-changelog2plugins reuse this command
First indexed Jan 1, 2026
/devkit.generate-changelogGenerates and updates project changelogs from Git history following Keep a Changelog and Conventional Commits. Also supports init, release, preview, and validate actions.
/changelog-generatorGenerates changelogs and release notes from conventional commits with automatic semantic versioning. Also supports updating existing changelogs and creating release notes for GitHub/GitLab.
/changelogAnalyzes git history since last release, detects undocumented changes, drafts entries for CHANGELOG.md [Unreleased] section, and updates on confirmation.
/validateValidates an upgrade.md file, checking for correct format and required sections.