updating-changelog

To generate a changelog draft from git diff, the skill analyzes branch changes relative to the next branch using git diff next...HEAD. It then structures the detected changes into draft entries for editors to review and publish.

Automated changelog generation works by reading .release-please-manifest.json to determine target documentation files, then comparing the current branch to next using git diff. It drafts structured entries based on the differences found.

Yes, you can use this skill to update migration notes and release documentation for contract developers and node operators. It drafts structured entries from branch changes and applies them to the appropriate documentation files.

The best way to document breaking changes is to run this skill before finalizing a PR. It analyzes the git diff between your branch and next, generating a structured changelog draft that covers the breaking changes for review.

Yes, you need a .release-please-manifest.json file in your repository. The skill reads this manifest to determine the target documentation files where the drafted changelog entries and migration notes will be applied.

No, generated changelog entries are not published automatically. The skill creates a draft from the git diff analysis that editors must then review and publish to the appropriate documentation files.