Agent skill
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/create-changelog
SKILL.md
Create Changelog
Create a changelog backfilled with version history.
Step 1: Run /changelog-rules Skill
Run /changelog-rules to load shared changelog conventions.
Step 2: Backfill Version History
Collect release history from the most authoritative source available:
- GitHub releases (preferred): Run
gh release list --limit 100 --json tagName,name,publishedAt,bodyto get release notes. For each release, parse the body into changelog entries. - Git tags (fallback): If no GitHub releases exist, run
git tag --sort=-v:refnameto list tags. For each consecutive tag pair, rungit log <older-tag>..<newer-tag> --onelineto collect commit summaries.
For each version, classify entries into the standard change types and apply the changelog-worthiness criteria per /changelog-rules.
Step 3: Check for Existing Changelog
If the changelog file already exists, warn the user and confirm before overwriting.
Step 4: Write Changelog
Write the changelog following the /changelog-rules file structure and conventions.
Step 5: Present the Result
Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?