releasenote
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.zipInstalls 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).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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| releasenote (this skill) | 1 | 4mo | No flags | Beginner |
| pr-draft-summary | 3 | 8mo | No flags | Beginner |
| codex-cli-bridge | 9 | 1y | Review | Intermediate |
| mflux-release | 1 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by DataDog
View all by DataDog →You might also like
pr-draft-summary
openai
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
mflux-release
filipstrand
Prepare a release in mflux (version bump, changelog, uv lock) without tagging/publishing.
code-changelog
bear2u
AI가 만든 모든 코드 변경사항을 reviews 폴더에 기록하고 간단한 HTML 뷰어로 웹 브라우저에서 실시간 확인할 수 있습니다. 매 수정마다 문서가 생성되고 Python 서버로 즉시 확인 가능합니다.
docstring
pytorch
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
report-research
numerai
Write a complete Numerai experiment report in experiment.md (abstract, methods, results tables, decisions, next steps) and generate/link the standard show_experiment plot(s). Use after running any Numerai research experiments, or when a user asks for a “full report”, “write up”, “experiment.md update”, or “generate the standard plot”.