generate-upgrade-notes

To automatically generate upgrade notes from a pull request, you need a tool that analyzes code diffs and commit messages. This Skill identifies feature movements, modifications, and backward-incompatible changes to create structured documentation files for your release.

Documenting backward-incompatible changes in a pull request requires analyzing code diffs to detect breaking modifications. This Skill automates that process by evaluating your changes and producing organized upgrade note files that detail these breaking changes for the next release.

Code diff analyzers identify feature movements by examining the modifications within a pull request. This Skill specifically evaluates code changes and commit messages to detect when features are moved or altered, organizing the results into structured documentation files.

Yes, you can use automated upgrade notes generation for package-first development. This Skill adheres to package-first development principles and specific file naming conventions while analyzing pull request changes to generate structured documentation.

Yes, you need subagents to fetch PR data for generating release notes in this workflow. The Skill requires subagents to retrieve pull request information and analyze code changes before creating the structured upgrade note files.

A limitation of automating pull request documentation with code analysis is the dependency on subagents for fetching PR data and evaluating changes. Additionally, the output strictly requires specific file naming conventions and adherence to package-first development principles to function correctly.