dk-changelog

Generate changelog entries from git changes and prepend them to CHANGELOG.md.

87|12|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/deepklarity/harness-kit --skill dk-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dk-changelog
Source: https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/dk-changelog
Command: npx skills add https://github.com/deepklarity/harness-kit --skill dk-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of changelog entries by parsing git diffs, prepending them to CHANGELOG.md, and optionally opening a PR to publish releases.

Core Features & Use Cases

  • Generate changelog entries from git changes.
  • Prepend new entries to CHANGELOG.md to maintain a chronological release history.
  • Optionally commit changes and open a PR to integrate the new changelog into release workflows.

Quick Start

Use the dk-changelog skill to generate a changelog entry from the current git changes.

Frequently Asked Questions about dk-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a changelog from git diffs?

Automatically generate a changelog by parsing git diffs, formatting them into a new entry, and prepending it to CHANGELOG.md to maintain chronological release history.

Can I automatically create a pull request for release notes?

Yes, after generating release notes and updating CHANGELOG.md, you can use PR mode to commit the changes and automatically open a pull request to integrate them.

What do I need to set up before automating changelog generation?

You need a local git repository containing a CHANGELOG.md file, along with integration configured for PR workflows to enable commit and pull request modes.

Does this changelog automation support a dry-run mode?

Yes, dry-run mode is supported alongside commit and PR modes, allowing you to preview formatted git diffs before modifying CHANGELOG.md or opening a pull request.

What is the best way to maintain a chronological changelog history from git changes?

The best way is to prepend new formatted git diff entries to CHANGELOG.md, ensuring recent release notes always appear at the top while preserving the chronological order.

Why is my automated changelog workflow not updating release notes correctly?

Automated changelog workflows require valid git diffs and an existing CHANGELOG.md file; missing prerequisites or incorrect PR workflow integration will prevent release notes from updating.