Skip to content

Add a skills for adding changelog entries and updating package versions#9781

Merged
kenzieschmoll merged 10 commits into
flutter:masterfrom
kenzieschmoll:clskill
Apr 17, 2026
Merged

Add a skills for adding changelog entries and updating package versions#9781
kenzieschmoll merged 10 commits into
flutter:masterfrom
kenzieschmoll:clskill

Conversation

@kenzieschmoll
Copy link
Copy Markdown
Member

@kenzieschmoll kenzieschmoll commented Apr 17, 2026

Adds skills to update package version numbers and add Changelog entries for published devtools packages: devtools_shared, devtools_app_shared, devtools_extensions.

Tests: not required for skills content. Skills validated through dart_skills_lint

Fixes #9778, #9780

Pre-launch Checklist

General checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read the Flutter Style Guide recently, and have followed its advice.
  • I signed the CLA.
  • I updated/added relevant documentation (doc comments with ///).

Issues checklist

Tests checklist

  • I added new tests to check the change I am making...
  • OR there is a reason for not adding tests, which I explained in the PR description.

AI-tooling checklist

  • I did not use any AI tooling in creating this PR.
  • OR I did use AI tooling, and...
    • I read the AI contributions guidelines and agree to follow them.
    • I reviewed all AI-generated code before opening this PR.
    • I understand and am able to discuss the code in this PR.
    • I have verifed the accuracy of any AI-generated text included in the PR description.
    • I commit to verifying the accuracy of any AI-generated code or text that I upload in response to review comments.

Feature-change checklist

  • This PR does not change the DevTools UI or behavior and...
    • I added the release-notes-not-required label or left a comment requesting the label be added.
  • OR this PR does change the DevTools UI or behavior and...
    • I added an entry to packages/devtools_app/release_notes/NEXT_RELEASE_NOTES.md.
    • I included before/after screenshots and/or a GIF demo of the new UI to my PR description.
    • I ran the DevTools app locally to manually verify my changes.

build.yaml badge

If you need help, consider asking for help on Discord.

@kenzieschmoll kenzieschmoll requested a review from a team as a code owner April 17, 2026 20:49
@kenzieschmoll kenzieschmoll requested review from elliette and srawlins and removed request for a team April 17, 2026 20:49
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces two new AI skill definitions for managing changelog entries and package versions within the DevTools repository. The review identified that both new Markdown files are missing the required copyright headers. Additionally, there are concerns regarding the consistency of changelog header levels and version suffixes compared to existing packages, as well as a need for a rule to prevent published packages from depending on unpublished ones.

Comment thread .agents/skills/adding-changelog-entries/SKILL.md
Comment thread .agents/skills/updating-package-versions/SKILL.md
Comment thread .agents/skills/adding-changelog-entries/SKILL.md Outdated
Comment thread .agents/skills/updating-package-versions/SKILL.md
Comment thread .agents/skills/adding-changelog-entries/SKILL.md Outdated

When adding changelog entries to published packages (`devtools_shared`, `devtools_app_shared`, and `devtools_extensions`), follow these rules:

- **Check Publication State**: Never add an entry to an already published version (e.g. `# 12.1.0`). You MUST check which versions are published on pub.dev (e.g., at `https://pub.dev/packages/<package_name>/versions`) before determining section headers! If a version is not yet published, it should be suffixed with the next numeric `-wip` tag (e.g., `## 0.5.1-wip`) or follow the existing convention in the file, such as `(not released)`. You should also match the existing header level (H1 or H2) used for versions in that file. Avoid generic placeholder headers like `# WIP`!
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we direct the agent to https://pub.dev/api/packages/<package> instead? Not sure if this is better or worse honestly. cc @jonasfj is there a way to filter that response to only the latest version?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will address as a follow up pending @jonasfj's response.

Comment thread .agents/skills/adding-changelog-entries/SKILL.md
@kenzieschmoll kenzieschmoll merged commit afcbeed into flutter:master Apr 17, 2026
87 of 88 checks passed
@kenzieschmoll kenzieschmoll deleted the clskill branch April 17, 2026 23:05
rishika0212 pushed a commit to rishika0212/devtools that referenced this pull request Apr 21, 2026
…ns (flutter#9781)

* Add a skill for adding changelog entries to DevTools packages

* Add skill for updating package versions that is used from the changelog skill

* add exception for copyright requirement

* address comments

* Update .agents/skills/adding-changelog-entries/SKILL.md

Co-authored-by: Jacob MacDonald <jakemac@google.com>

* Update .agents/skills/adding-changelog-entries/SKILL.md

Co-authored-by: Jacob MacDonald <jakemac@google.com>

* whitespace

---------

Co-authored-by: Jacob MacDonald <jakemac@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[devtools velocity] [skills] Add Skill for adding Changelog entries to published packages

3 participants