Adding Release Notes Agent Skill

Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXT_RELEASE_NOTES.md file.

2k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

1727

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/flutter/devtools --skill adding-release-notes

What comes with it

2 294 bytes besides the instruction

scripts/add_note.dart

The instruction itself

10 sections, as written by the author

Adding Release Notes

This skill helps automate adding release notes to packages/devtools_app/release_notes/NEXT_RELEASE_NOTES.md.

Workflow

Copy this checklist into your response to track progress:

Release Notes Progress:
- [ ] Step 1: Formulate the entry (past tense)
- [ ] Step 2: Find the PR number (if not already known)
- [ ] Step 3: Determine the section (Inspector, Memory, etc.)
- [ ] Step 4: Add the entry (use scripts/add_note.dart)
- [ ] Step 5: Add images (if applicable)

Guidelines

1. Identify the PR Number

If the PR number is unknown, use the following methods to find it:

Local Branch: Identify the branch name using git branch or git log. If the branch is pushed to origin, it often has a linked PR.
GitHub CLI (gh): Use the GitHub CLI to find the PR associated with the current branch.
IMPORTANT: Always use PAGER=cat to prevent gh from hanging in non-interactive terminals.
Command: PAGER=cat gh pr list --head <branch_name> --json number,title
Search by Change Description: Search open PRs using keywords from your change title or description.
Command: PAGER=cat gh pr list --search "<keywords>" --limit 5
Web Search: If CLI tools fail, use search_web to find the PR on GitHub:
Query: site:github.com/flutter/devtools "Add support for searching within the log details view"

2. Formulate the Entry

Tense: Always use past tense (e.g., "Added", "Improved", "Fixed").
Punctuation: Always end entries with a period.
Template: * <Description>. #<PR_NUMBER>
Placeholder: Use TODO if you have exhausted all search methods and the PR has not been created yet.
Images: If adding an image, indent it by two spaces to align with the bullet point, and ensure there is only one newline between the text and the image.
Correct Format:

    - Added support for XYZ. [#TODO](https://github.com/flutter/devtools/pull/TODO)
      ![](images/my_feature.png)

Examples:
* Added support for XYZ. #12345
* Fixed a crash in the ABC screen. #67890

3. User-Facing Changes Only

Criteria: Focus on what changed for the user, not how it was implemented.
Avoid: Technical details like "Implemented XYZ with a new controller", "Updated the build method", or naming internal classes.
Example (Bad): * Implemented log details search using SearchControllerMixin. #TODO
Example (Good): * Added search support to the log details view. #TODO

4. Determine Section

Match the change to the section in NEXT_RELEASE_NOTES.md:

General updates
Inspector updates
Performance updates
CPU profiler updates
Memory updates
Debugger updates
Network profiler updates
Logging updates
App size tool updates
Deep links tool updates
VS Code sidebar updates
DevTools extension updates
Advanced developer mode updates

5. Add to NEXT_RELEASE_NOTES.md

Use the provided utility script to insert the note safely. The script handles replacing the TODO placeholder if it's the first entry in that section.

dart .agents/skills/adding-release-notes/scripts/add_note.dart "Inspector updates" "Added XYZ support" TODO

6. Optional: Images

Add images to packages/devtools_app/release_notes/images/ and reference them:

![Accessible description](images/screenshot.png "Hover description")

Constraint: Use dark mode for screenshots.

Resources

README.md: Official project guidance.

Other skills for the same job

different authors, same section of the catalogue

DOCX

by anthropics

vendor ×16

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

3k tokens

How to use it

Copy the folder

Take flutter/adding-release-notes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.