What format does this skill follow?

It follows the 'Keep a Changelog' standard, utilizing specific sections like Added, Changed, Fixed, and Security with ISO 8601 date formatting.

How do I provide data to the skill?

Claude uses this skill to analyze your git log and PR data to generate the draft entries according to the specified formatting rules.

How does it filter git history?

The skill provides guidelines to exclude internal dependency updates, CI/CD changes, and refactors that don't have user-visible effects.

Does it handle contributor recognition?

Yes, the skill includes logic to distinguish between first-time and returning contributors, providing standardized attribution strings for each.

Can I use this for non-Rust projects?

While it includes conventions for Rust-specific items like MSRV, the core logic for structured changelogs is applicable to any software project.

Prepare Changelog

Name: Prepare Changelog
Author: Microck

byMicrock

•

Developer Tools

Automates the creation of professional release notes following the Keep a Changelog standard and Nextest conventions.

About

This skill provides specialized guidance for Claude to generate structured, user-focused changelogs. It implements the 'Keep a Changelog' format, ensuring that release entries are categorized correctly into sections like Added, Fixed, and Security. The skill is particularly adept at handling technical project nuances, such as Minimum Supported Rust Version (MSRV) changes, contributor attribution for open-source projects, and the extraction of meaningful updates from git commit logs while filtering out internal noise.

Key Features

Structured handling of breaking changes, MSRV updates, and security fixes
Guidelines for linking GitHub PRs, issues, and external documentation
81 GitHub stars
Smart filtering of internal refactoring vs. user-visible feature updates
Automated contributor attribution for first-time and returning developers
Standardized Keep a Changelog formatting for version headers and sections

Use Cases

Generating release notes from git commit history before a new version launch
Formatting community contributions and ensuring proper author attribution
Maintaining a consistent and readable history for open-source project repositories

About

Key Features

Structured handling of breaking changes, MSRV updates, and security fixes
Guidelines for linking GitHub PRs, issues, and external documentation
81 GitHub stars
Smart filtering of internal refactoring vs. user-visible feature updates
Automated contributor attribution for first-time and returning developers
Standardized Keep a Changelog formatting for version headers and sections

Use Cases

Generating release notes from git commit history before a new version launch
Formatting community contributions and ensuring proper author attribution
Maintaining a consistent and readable history for open-source project repositories