Flutter Pub Release
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
Adds user-facing change descriptions to DevTools release notes.
Install Adding Release Notes
$ npx skills add flutter/devtools --skill adding-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter/devtools adding-release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-release-notes .claude/skills/adding-release-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .claude/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flutter/devtools --skill adding-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter/devtools adding-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-release-notes .agents/skills/adding-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .agents/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/devtools --skill adding-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter/devtools adding-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-release-notes .cursor/skills/adding-release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .cursor/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flutter/devtools.git --path .agents/skills/adding-release-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flutter/devtools --skill adding-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter/devtools adding-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-release-notes .gemini/skills/adding-release-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .gemini/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flutter/devtools adding-release-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flutter/devtools --skill adding-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-release-notes .github/skills/adding-release-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .github/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/devtools --skill adding-release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flutter/devtools adding-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-release-notes .opencode/skills/adding-release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adding-release-notes" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/adding-release-notes into .opencode/skills/adding-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-release-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
adding-release-notes- GitHub stars
- 1.7k
- Token cost
- ~1k tokens
- SKILL.md length
- 398 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Adds user-facing change descriptions to DevTools release notes.
- Works in 6 steps: Identify the PR Number → Formulate the Entry → User-Facing Changes Only → …
- Documenting improvements
- SKILL.md covers Workflow, Guidelines and Resources
- Runs Dart scripts from its folder; calls git, gh and dart
What it does
Adding Release Notes is an agent skill from flutter/devtools. Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXTRELEASENOTES.md file.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts.
It sits in Development, covering Changelog and release notes. It works with Flutter and GitHub. The repository describes itself as: Developer tools for Flutter & Dart. The licence is BSD-3-Clause.
When your agent uses it
- Documenting improvements
- New features in the NEXTRELEASENOTES.md file
Example prompts
- “/adding-release-notes”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3a3b64a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Dart), which the agent can run.
Shell commands in SKILL.md call:
gitghdart
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Adding Release Notes loads about 1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 398 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from flutter/devtools at commit 3a3b64a, republished under its BSD-3-Clause licence (© flutter). 398 words, ~1,023 tokens.
Download SKILL.mdSave it as
.claude/skills/adding-release-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- adding-release-notes
- description
- Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXT_RELEASE_NOTES.md file.
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 branchorgit 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=catto preventghfrom hanging in non-interactive terminals. - Command:
PAGER=cat gh pr list --head <branch_name> --json number,title
- IMPORTANT: Always use
- 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
- Command:
- Web Search: If CLI tools fail, use
search_webto find the PR on GitHub:- Query:
site:github.com/flutter/devtools "Add support for searching within the log details view"
- Query:
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>](https://github.com/flutter/devtools/pull/<PR_NUMBER>) - Placeholder: Use
TODOif 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:
markdown - Added support for XYZ. [#TODO](https://github.com/flutter/devtools/pull/TODO) 
- Correct Format:
- Examples:
* Added support for XYZ. [#12345](https://github.com/flutter/devtools/pull/12345)* Fixed a crash in the ABC screen. [#67890](https://github.com/flutter/devtools/pull/67890)
Show full SKILL.md (153 more words)Show less
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](https://github.com/flutter/devtools/pull/TODO) - Example (Good):
* Added search support to the log details view. [#TODO](https://github.com/flutter/devtools/pull/TODO)
4. Determine Section
Match the change to the section in NEXT_RELEASE_NOTES.md:
General updatesInspector updatesPerformance updatesCPU profiler updatesMemory updatesDebugger updatesNetwork profiler updatesLogging updatesApp size tool updatesDeep links tool updatesVS Code sidebar updatesDevTools extension updatesAdvanced 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" TODO6. Optional: Images
Add images to packages/devtools_app/release_notes/images/ and reference them:
Constraint: Use dark mode for screenshots.
Resources
- README.md: Official project guidance.
© flutter, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in .agents/skills/adding-release-notes of flutter/devtools.
- SKILL.md
- scripts/add_note.dart
Open the folder on GitHubat commit 3a3b64a
Compare with similar skills
Adding Release Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Adding Release Notes this skillflutter/devtools | 1.7k | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Flutter Pub ReleaseMixinNetwork/flutter-plugins | 512 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
More from flutter/devtools
All 10 skills in this repoAdding Copyright Headers
flutter/devtools
Adds copyright headers to files based on file type. An agent skill from flutter/devtools.
Debugging Devtools Extensions
flutter/devtools
Guidelines and step-by-step workflow for debugging DevTools extensions locally, including stub mode, fixed-port launching, browser auto-opening, URL query parameters, target app connection, and…
Reviewing PRs
flutter/devtools
General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting.
Closing Obsolete Issues
flutter/devtools
Find and close obsolete, stale, or not reproducible issues in the flutter/devtools repository.
Reviewing Devtools PRs
flutter/devtools
DevTools repository-specific PR review workflow enforcing DevTools style guidelines and common review patterns.
Adding Changelog Entries
flutter/devtools
A skill your agent uses when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions.
Related
Categories
Questions about Adding Release Notes
What does Adding Release Notes do?
Adds user-facing change descriptions to DevTools release notes. Adding Release Notes is an agent skill from flutter/devtools. Adds user-facing change descriptions to DevTools release notes.
When should I use Adding Release Notes?
Adding Release Notes fits situations like: documenting improvements; new features in the NEXTRELEASENOTES.md file.
How do I install Adding Release Notes in Claude Code?
Run `npx skills add flutter/devtools --skill adding-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/adding-release-notes in flutter/devtools) into .claude/skills/adding-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Adding Release Notes in Codex?
Run `npx skills add flutter/devtools --skill adding-release-notes -a codex`. Or copy the skill folder (.agents/skills/adding-release-notes in flutter/devtools) into .agents/skills/adding-release-notes in your project. Codex loads it when a task matches its description.
Can I use Adding Release Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter/devtools --skill adding-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-release-notes, .gemini/skills/adding-release-notes, .github/skills/adding-release-notes and .opencode/skills/adding-release-notes in your project.
What does Adding Release Notes need to run?
Going by SKILL.md and its folder, Adding Release Notes needs Dart for the scripts in its folder and the command-line tools its instructions call (git, gh and dart).
Does Adding Release Notes access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Adding Release Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Adding Release Notes use?
Adding Release Notes is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Adding Release Notes use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Adding Release Notes?
Skills that share tags, products or a category with Adding Release Notes: Flutter Pub Release (MixinNetwork/flutter-plugins, 512 stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Adding Release Notes?
flutter (a GitHub organization) maintains it in flutter/devtools, which has 1,732 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: flutter/devtools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.