hiddink-harness-release-notes

Generate structured release notes and update CHANGELOG.md from git commits and closed GitHub issues.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiddink-harness-release-notes
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/omcustom-release-notes
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of aggregating git history and issue tracking data to produce consistent, professional release documentation.

Core Features & Use Cases

  • Automated Classification: Automatically categorizes commits into Conventional Commit groups like features, bug fixes, and security updates.
  • Changelog Maintenance: Seamlessly promotes unreleased changes to versioned sections in your CHANGELOG.md file.
  • Use Case: After completing a development cycle, use this skill to instantly generate a formatted release summary and update your project history without leaving your coding environment.

Quick Start

Invoke the release notes generator by providing the target version number to the skill command.

Frequently Asked Questions about hiddink-harness-release-notes

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

FAQPage Schema
How do I automate release notes generation from git commit history?

Automate release notes generation by using a script that analyzes git commit history and closed GitHub issues to produce structured, categorized documentation. This eliminates manual aggregation of repository metadata for version tracking.

How does automated changelog maintenance work with Conventional Commits?

Automated changelog maintenance works by parsing commit history and categorizing entries into Conventional Commit groups like features, bug fixes, and security updates. It seamlessly promotes unreleased changes into versioned sections in your CHANGELOG.md file.

Do I need the GitHub CLI to generate project release documentation?

Yes, you need the GitHub CLI to generate release documentation, alongside git and python3. The skill requires these dependencies to query repository metadata and perform file system updates during local development sessions.

What's the best way to update a CHANGELOG.md file after a development cycle?

The best way to update a CHANGELOG.md file is to invoke an automated release notes generator with a target version number. This instantly generates a formatted release summary and updates your project history without leaving your coding environment.

Can I categorize git commits into features and bug fixes automatically?

Yes, you can categorize git commits automatically by analyzing the commit history against Conventional Commit standards. The script automatically groups commits into features, bug fixes, and security updates for structured documentation.