CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs:changelog

Generate a changelog entry from recent git commits. Use when preparing a release or documenting what changed between versions.

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

Changelog Generator

Generate a formatted changelog entry from git commit history between two tags.

Steps

Step 1: Determine Range

If only from-tag is provided, use HEAD as the end point. If both tags are provided, generate the changelog for commits between them.

git log ${from_tag}..${to_tag} --oneline --no-merges

Step 2: Categorize Commits

Group commits by type using conventional commit prefixes:

  • feat: -> Features
  • fix: -> Bug Fixes
  • docs: -> Documentation
  • refactor: -> Refactoring
  • test: -> Tests
  • chore: -> Maintenance

Commits without a recognized prefix go into "Other Changes".

Step 3: Format Changelog

Output in Keep a Changelog format:

## [version] - YYYY-MM-DD

### Features
- Description (commit-hash)

### Bug Fixes
- Description (commit-hash)

### Documentation
- Description (commit-hash)

Step 4: Check for Breaking Changes

Search commit messages and bodies for "BREAKING CHANGE:" or commits with ! after the type prefix. If found, add a "Breaking Changes" section at the top of the changelog entry.

git log ${from_tag}..${to_tag} --grep="BREAKING CHANGE" --format="%h %s"
Repository

LuminairPrime/git-worktrees-prime

Path

vendors/cc-skill-main/eval/runs/cc-skill-enhancer-eval/2026-06-01-opus/cases/case-005-medium-with-scripts/_modified/target-skill/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.