Generate GitHub release notes for shelli releases using structured templates.
npx skills add https://github.com/schovi/shelli --skill release-notes-skill-schovi
Please help me install this Agent Skill. Skill: Release Notes Skill Source: https://github.com/schovi/shelli/tree/main/.claude/skills/release Command: npx skills add https://github.com/schovi/shelli --skill release-notes-skill-schovi
This skill helps teams generate consistent GitHub release notes for shelli releases, ensuring a clear and complete changelog.
Provide a release notes draft for the latest shelli tag using the standard template.
High-intent search queries and answers about installing and using this skill.
Generate GitHub release notes for shelli releases by applying a structured template that summarizes changes and guides users through breaking changes and migrations. The output covers breaking changes, new features, bug fixes, migration notes, and a brief usage summary as applicable to the tag.
Automate changelog creation for GitHub tags using a template-driven approach that applies a standard format to multiple releases. This reduces manual drafting time and ensures release notes follow a defined structure covering breaking changes, features, fixes, and migrations.
A specific template structure for GitHub release notes is needed to ensure a clear and complete changelog. The required structure includes sections for breaking changes, new features, bug fixes, migration notes, and a brief usage summary as applicable to the tag.
The release notes generator includes a migration example if changes affect usage. It follows a defined structure that features a 'Breaking Changes' section when needed, ensuring users are guided through any breaking changes and migrations.
You can use this template for GitHub releases without manual formatting because it is template-driven. It applies a standard format to multiple releases, reducing manual drafting time while maintaining a consistent structure and detail level across shelli versions.
GitHub release notes for breaking changes should contain a dedicated 'Breaking Changes' section and a migration example if changes affect usage. They also need to cover new features, bug fixes, migration notes, and a brief usage summary as applicable to the tag.
trevorbyrumGenerate a changelog, bump version, draft release notes, and stage a git tag.
typemdGather closed issues and commits to draft release notes and create a GitHub draft release.
anssipAutomates project releases by updating changelog, tagging git commits for CI.
SumitRajpalGenerate a Markdown changelog from Git history using conventional commits.
