...
npx skills add https://github.com/ponylang/llm-skills --skill pony-release-notes
Please help me install this Agent Skill. Skill: pony-release-notes Source: https://github.com/ponylang/llm-skills/tree/main/pony-release-notes Command: npx skills add https://github.com/ponylang/llm-skills --skill pony-release-notes
Streamline the creation of user-facing release notes and CHANGELOG entries for Pony projects. This guide ensures end users understand what changed and why it matters, while helping maintainers stay consistent across releases.
Create a new markdown file in the .release-notes/ directory with a unique, descriptive name and a user-facing title.
High-intent search queries and answers about installing and using this skill.
Pony release notes should describe user-visible changes in user terms, not internal refactoring. This means summarizing new features, bug fixes, and breaking changes with clear examples so end users understand what changed and why it matters.
Documenting breaking changes in a Pony changelog requires including before and after code snippets alongside migration guidance. This approach ensures users can smoothly transition between Pony versions by seeing exactly what code needs updating.
Categorizing Pony changelog entries is best done by splitting notes into Added, Fixed, and Changed sections. This convention aligns with automation labels and helps maintainers stay consistent across releases while making changes easy to scan.
To align Pony release notes with PR workflow automation, create a new markdown file in the .release-notes/ directory using a unique, descriptive name and a user-facing title, then apply automation labels to categorize the entry by type.
Pony release notes need before and after snippets for breaking changes because they provide clear migration guidance. Showing the exact code transformation helps end users quickly understand how to update their projects without guessing.
Yes, standard changelog formatting works for Pony release notes if entries are categorized by type (Added, Fixed, Changed) and written with an end-user focus, ensuring descriptions explain user-visible changes rather than internal refactoring.
dagbaConvert git history into App Store release notes with bullet-based themes.
aaronjmarsAnalyze recent GitHub commits and generate categorized Markdown changelogs.
jayteealaoGenerate changelog entries from git commits into Added, Changed, Fixed, and Breaking sections.
FutureAtomsGenerate and update changelogs in Keep a Changelog format from Git commit history.
