Compile user-facing changelogs for Paperclip calver stable releases.
npx skills add https://github.com/khoabd/paperclip --skill release-changelog-khoabd
Please help me install this Agent Skill. Skill: release-changelog Source: https://github.com/khoabd/paperclip/tree/main/.agents/skills/release-changelog Command: npx skills add https://github.com/khoabd/paperclip --skill release-changelog-khoabd
Manually compiling accurate, user-facing changelogs for Paperclip's stable releases is time-consuming and error-prone, requiring cross-referencing commits, changesets, and merged pull requests while adhering to the project's calendar versioning rules and contributor attribution guidelines.
Use the release-changelog skill to generate the user-facing changelog for the next Paperclip stable release using recent commits, changesets, and merged pull requests.
High-intent search queries and answers about installing and using this skill.
Automating changelog generation for calver stable releases involves aggregating commit data, changeset files, and merged pull request context to compile accurate release documentation. This process automatically categorizes user-facing changes and applies compliant contributor attribution.
Breaking change detection works by analyzing aggregated commit history and changeset files to flag breaking changes. The generated release notes then include clear, user-facing upgrade paths alongside each detected breaking change.
Yes, you can automatically exclude bots and core team members from contributor attribution. The changelog compilation process applies compliant attribution rules, listing external contributors by GitHub username while omitting bot accounts and core maintainers.
You prevent overwriting existing changelog files through idempotency checks. Before generating new release documentation, the system performs idempotency checks to ensure existing changelog files remain untouched during the automation process.
Yes, automated release documentation supports categorizing changes into structured user-facing sections. The generated changelog organizes changes into categories like Breaking Changes, Highlights, Improvements, and Fixes to align with documentation standards.
The best way to compile user-facing changelogs is to aggregate merged pull request context and changeset files since the last stable tag. This ensures no relevant changes are missed and the output formatting aligns with release documentation standards.
santhank8Generate a calver-aligned release changelog from commits, changesets, and merged PRs.
elijahbowieGenerate stable release changelogs from commits, changesets, and merged PRs.
kabakaSchedule and enforce CalVer releases with automated changelog and git tag updates.
louisfbuysGenerate a Markdown changelog from Git commits, changesets, and merged pull requests.
