How are contributors recognized in the changelog?

The skill differentiates between first-time and returning contributors, using specific templates to thank them and link to their GitHub profiles.

Does it support links to PRs and Issues?

Yes, it uses inline markdown links and ensures PRs use /pull/ URLs while issues use /issues/ URLs, with definitions placed at the end of the entry.

What format does this skill use for changelogs?

It follows the Keep a Changelog specification, organizing entries into sections like Added, Changed, Fixed, and Security using ISO 8601 date formats.

Can I use this for non-Nextest projects?

While optimized for the nextest-rs repository, the underlying logic follows general Keep a Changelog best practices suitable for most software projects.

Prepare Changelog

Name: Prepare Changelog
Author: nextest-rs

bynextest-rs

•

2,732

Developer Tools

Generates and formats standardized changelog entries for Nextest releases following the Keep a Changelog specification.

About

The Prepare Changelog skill provides domain-specific guidance for maintaining the nextest-rs/nextest release history, ensuring every entry adheres to strict formatting and structural standards. It assists maintainers in categorizing changes into organized sections like Added, Fixed, and Security, while managing complex tasks such as contributor attribution, GitHub issue linking, and distributor-specific notations. By enforcing the Keep a Changelog format and ISO 8601 date conventions, this skill ensures that project documentation remains professional, consistent, and easy for both users and automated tools to parse.

Key Features

Standardized contributor attribution for first-time and returning authors
Enforcement of ISO 8601 date formats and bracketed version headers
Precise formatting for PR, Issue, and security advisory links
2,732 GitHub stars
Automated categorization of changes into standard Keep a Changelog sections
Support for specialized blocks like 'Note to distributors' and 'Experimental Features'

Use Cases

Drafting detailed release notes for a new version of cargo-nextest
Ensuring first-time contributors are properly credited in the project history
Aggregating multiple PR commits into a cohesive user-facing summary

About

Key Features

Standardized contributor attribution for first-time and returning authors
Enforcement of ISO 8601 date formats and bracketed version headers
Precise formatting for PR, Issue, and security advisory links
2,732 GitHub stars
Automated categorization of changes into standard Keep a Changelog sections
Support for specialized blocks like 'Note to distributors' and 'Experimental Features'

Use Cases

Drafting detailed release notes for a new version of cargo-nextest
Ensuring first-time contributors are properly credited in the project history
Aggregating multiple PR commits into a cohesive user-facing summary