changelog-manager

Create and update CHANGELOG.md entries with AI attribution and PRD context.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/dundas/uhr --skill changelog-manager-dundas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-manager
Source: https://github.com/dundas/uhr/tree/main/.claude/skills/changelog-manager
Command: npx skills add https://github.com/dundas/uhr --skill changelog-manager-dundas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of maintaining a CHANGELOG.md file, ensuring all changes are documented with proper attribution to the AI model or CLI that made them, along with relevant context from PRDs and tasks.

Core Features & Use Cases

  • Automated Entry Creation: Generates changelog entries based on user input or automated triggers (like PR merges).
  • AI Attribution: Automatically identifies and records which AI system made the change.
  • Contextual Linking: Includes links to PRDs, tasks, and PR numbers for better traceability.
  • Use Case: After merging a feature, this Skill can automatically add an entry to CHANGELOG.md detailing the feature, attributing it to the AI that assisted, and linking to the relevant PRD.

Quick Start

Use the changelog-manager skill to add a new entry for a fixed bug with the description "Resolved issue with user login".

Frequently Asked Questions about changelog-manager

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

FAQPage Schema
How do I automate CHANGELOG.md updates when merging pull requests?

Automate CHANGELOG.md updates by triggering entry creation on PR merges. The skill generates entries adhering to the Keep a Changelog format, incorporating contextual links to the PR number, PRD, and task references automatically.

What is the best way to add AI model attribution to a changelog entry?

Add AI model attribution to a changelog entry by using automated identification. The skill records which specific AI system or CLI made the change, embedding this metadata directly into the CHANGELOG.md file alongside the feature description.

Can I generate git commits and version release tags from a changelog?

Yes, you can generate git commits and version release tags directly from a changelog. The skill automates commit and tag generation for version releases, streamlining the release management process after entries are documented.

Does the Keep a Changelog format support bulk changelog operations and manual entries?

The Keep a Changelog format supports both manual entries and bulk operations. You can manually input descriptions like a fixed bug, or process bulk updates, ensuring all changes are documented with proper AI attribution and contextual linking.

Why should I include PRD context and task references in release documentation?

Include PRD context and task references in release documentation to ensure better traceability. Linking these elements within your CHANGELOG.md connects the documented changes directly to their originating product requirements and development tasks.

What are the limitations of using AI attribution for changelog management?

AI attribution for changelog management relies on correctly identifying the AI system or CLI involved. If the change lacks clear automated triggers or manual input specifying the AI source, the attribution metadata within the Keep a Changelog format may be incomplete.