RE

Helps developers create standardized release notes fragments for the dd-trace-py project.

Install

mkdir -p .claude/skills/releasenote && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3572" && unzip -o skill.zip -d .claude/skills/releasenote && rm skill.zip

Installs to .claude/skills/releasenote

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Decide whether a release note is needed, and if so create or update a Reno fragment, following dd-trace-py's conventions (docs/releasenotes.rst).
145 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Determine if a release note is required for a code change
  • →Generate a Reno fragment skeleton
  • →Edit the generated YAML to include relevant sections
  • →Verify facts against the code
  • →Write customer-visible symptoms for fixes

How it works

This skill analyzes code changes and project conventions to determine if a release note is needed, then generates and helps edit a Reno fragment.

Inputs & outputs

You give it
Code changes in the current branch and project conventions
You get back
A Reno fragment in YAML format, or a statement that no note is needed

When to use releasenote

  • →Creating release notes for bug fixes
  • →Documenting breaking changes
  • →Managing release fragments
  • →Updating project changelogs

About releasenote

Determines if a code change requires a release note and guides the user through generating a Reno fragment. It enforces project conventions for documenting user-facing changes.

Create or update release notes for changes in the current branch using Reno, following dd-trace-py's conventions and the guidelines in docs/releasenotes.rst.

When not to use it

  • →When documenting CI chores
  • →When documenting internal-only API changes
  • →When documenting test-only changes

Limitations

  • →The note is for a customer upgrading dd-trace-py, not a contributor
  • →Internal rationale, implementation detail, and CI/test notes go in the PR description, not here
  • →Never include internal function/class names, internal tag prefixes, RFC/JIRA/ticket numbers, CI job names, draft leftovers, or 'why we built it this way' rationale

How it compares

This skill automates the process of creating and formatting release notes according to specific project conventions, unlike manually drafting notes which can lead to inconsistencies.

Compared to similar skills

releasenote side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
releasenote (this skill)14moNo flagsBeginner
pr-draft-summary38moNo flagsBeginner
codex-cli-bridge91yReviewIntermediate
mflux-release18moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry