Adding Release Notes

This skill helps automate adding release notes to packages/devtoolsapp/releasenotes/NEXTRELEASENOTES.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>. #<PRNUMBER>
• 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.

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

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