adding-changelog-entries Skill
Use when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions. Published by flutter in devtools.
Decision snapshot
Is this a fit?
Developers using devtools, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago · BSD-3-Clause license
No specific cautions were detected. Review the source and requested permissions before installing.
What is adding-changelog-entries Skill?
Use when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions. Published by flutter in devtools. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using devtools
Declared skill metadata
- Source file: .agents/skills/adding-changelog-entries/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use adding-changelog-entries Skill
- Use it for developers using devtools.
Built with
Editorial notes
Source
- Creator: flutter
- Repository: flutter/devtools
- Skill file: .agents/skills/adding-changelog-entries/SKILL.md
What it does
Use when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions.
Skill instructions
Adding Changelog Entries When adding changelog entries to published packages (devtoolsshared, devtoolsappshared, and devtoolsextensions), 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/<packagename/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! - New Version Headers: If a version bump is required, you MUST first use the instructions in updating-package-versions to update the package version in pubspec.yaml, and then add a new header to the changelog file with the new version (e.g., 0.5.1-wip) before adding your entries. - Accur
Verified compatibility and discovery
Frequently asked questions
What is adding-changelog-entries?
adding-changelog-entries is a open-source AI agent skill with Copy skill directory. Use when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions.
Who is adding-changelog-entries best for?
adding-changelog-entries is best for reusing agent instructions, scripts, and references.
How do I install adding-changelog-entries?
Install or run adding-changelog-entries using Copy skill directory. Check adding-changelog-entries for the latest setup command.
Is adding-changelog-entries actively maintained?
adding-changelog-entries may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
