releasenote

Automate release note creation by using Reno to generate per-change YAML fragments in your releasenotes/notes/ directory. Run `riot run reno new <title-slug>` to start a new fragment, confirm the category (feature, bugfix, deprecation, or breaking-change), and the Skill outputs a formatted YAML file following your project's release-note conventions.

Reno is a release-note management tool that organizes changes as individual YAML fragment files stored in a dedicated notes directory. Each fragment describes a single change with category and description, and Reno combines them into a consolidated release note, eliminating merge conflicts and enforcing consistent formatting across contributors.

Yes, this Skill creates or updates release notes for changes on your current branch. After the Skill generates a YAML fragment under releasenotes/notes/, you can edit it to refine the description, category, and wording before it merges into your final release notes.

The Skill outputs YAML fragments with a .yaml suffix stored under releasenotes/notes/. Each fragment contains the change category, slug identifier, and user-facing description, conforming to Reno's structure and your project's docs/releasenotes.rst conventions.

The Skill uses guided prompts to confirm the change category—feature, bugfix, deprecation, or breaking-change—before generating the fragment. You validate the category during the workflow; the Skill enforces consistency with your project's Reno-based release-note process.

You need Reno installed, riot configured for your project, and changes committed to your current branch. The Skill expects your project to follow dd-trace-py conventions with a docs/releasenotes.rst file and a releasenotes/notes/ directory already established.