Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/changelog
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/changelog/SKILL.md \
-o ~/.claude/skills/changelog/SKILL.md Generate Keep a Changelog entries from git history and validate commit message format.
/changelog generate [--from-tag <tag>] [--to-tag <tag>] Generate changelog entries
/changelog lint [--from-ref <ref>] [--to-ref <ref>] Lint commit messages
/changelog generate --from-tag v2.0.0
/changelog lint --from-ref main --to-ref dev
/changelog generate --from-tag v2.0.0 --to-tag v2.1.0 --format markdown
engineering/skills/changelog-generator/scripts/generate_changelog.py — Parse commits, render changelog (--from-tag, --to-tag, --from-ref, --to-ref, --format markdown|json)engineering/skills/changelog-generator/scripts/commit_linter.py — Validate conventional commit format (--from-ref, --to-ref, --strict, --format text|json)→ engineering/skills/changelog-generator/SKILL.md
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment