Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
Install Updating Package Versions
$ npx skills add flutter/devtools --skill updating-package-versions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter/devtools updating-package-versions --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/updating-package-versions .claude/skills/updating-package-versions && 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 "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .claude/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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/updating-package-versionsType 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 updating-package-versions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter/devtools updating-package-versions --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/updating-package-versions .agents/skills/updating-package-versions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .agents/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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 updating-package-versions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter/devtools updating-package-versions --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/updating-package-versions .cursor/skills/updating-package-versions && 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 "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .cursor/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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/updating-package-versions--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 updating-package-versions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter/devtools updating-package-versions --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/updating-package-versions .gemini/skills/updating-package-versions && 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 "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .gemini/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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 updating-package-versionsInstalls 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 updating-package-versions -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/updating-package-versions .github/skills/updating-package-versions && 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 "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .github/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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 updating-package-versions -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 updating-package-versions --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/updating-package-versions .opencode/skills/updating-package-versions && 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 "updating-package-versions" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/updating-package-versions into .opencode/skills/updating-package-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "updating-package-versions", 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
updating-package-versions- GitHub stars
- 1.7k
- Token cost
- ~556 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
- Development work in your project
- Calls flutter
What it does
Updating Package Versions is an agent skill from flutter/devtools. Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Flutter. The repository describes itself as: Developer tools for Flutter & Dart. The licence is BSD-3-Clause.
When your agent uses it
- Development work in your project
Example prompts
- “Use the updating-package-versions skill to guide updating dependency versions in published packages to avoid mono-repo resolution failures”
- “/updating-package-versions”
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
Shell commands in SKILL.md call:
flutter
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Updating Package Versions loads about 556 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 272 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from flutter/devtools at commit 3a3b64a, republished under its BSD-3-Clause licence (© flutter). 272 words, ~556 tokens.
Download SKILL.mdSave it as
.claude/skills/updating-package-versions/SKILL.md (or your agent's skills folder).- name
- updating-package-versions
- description
- Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
Updating Package Versions
When updating dependency versions in published package pubspec.yaml files (devtools_shared, devtools_app_shared, and devtools_extensions), follow these rules to protect the local mono-repo workspace graph:
- Version Decisions: Decide if it should be a major, minor, or patch version based on your edits:
- Breaking changes: Major bump (+1 to first component, others reset to 0). E.g., removals of public constants, properties, getters/setters, or APIs.
- New features or deprecation start: Minor bump (+1 to second component, patch resets to 0).
- Bug fixes and non-breaking changes: Patch bump (+1 to third component).
- Match Exact Versions: Always use the actual version specified in the target package's
pubspec.yamlfile. - Suffix Preservation: If a requested version contains a suffix like
-wip(e.g.,13.0.0-wip), the full string MUST be used in dependency constraints (e.g.,devtools_shared: ^13.0.0-wip). - Prevent Graph Failures: Do not drop the suffix or estimate the base version tags. Version solver operations will fail in the local workspace if dependencies point to published strings that can't be resolved in non-published repositories.
- No Dependencies on Unpublished Packages: Published packages (
devtools_shared,devtools_app_shared, anddevtools_extensions) MUST NOT depend on unpublished packages likedevtools_appordevtools_test. - Resolution Testing: After updating versions, run
flutter pub getin the repository to ensure version solving is satisfied. If this returns errors, you should fix the errors and try again. - Updating devtools_app: In
packages/devtools_app/pubspec.yaml:- Dependencies on published packages do not have version constraints. This is intentional; do not change this when updating versions.
- Always use the
dt update-versiontool to update thedevtools_appversion. - This should only be updated for monthly releases and cherry pick releases, so perform this update only when explicitly asked to.
© 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
Just SKILL.md in .agents/skills/updating-package-versions of flutter/devtools.
Open the folder on GitHubat commit 3a3b64a
Compare with similar skills
Updating Package Versions 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 |
|---|---|---|---|---|---|---|
| Updating Package Versions this skillflutter/devtools | 1.7k | — | ~556 | Automated safety check: Pass | BSD-3-Clause | |
| Code Reviewflutter/flutter | 179k | — | ~1.4k | Automated safety check: Pass | BSD-3-Clause | |
| Senior Architect Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 8 repos | ~1.2k | Automated safety check: Notes | Custom licence | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Code Guidelinesgetsentry/sentry-dart | 873 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Git Worktree Setupk8zdev/k8z | 155 | — | ~930 | Automated safety check: Pass | None |
Similar skills
Senior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
- Official
Code Guidelines
getsentry/sentry-dart
Enforce Sentry Dart/Flutter SDK code guidelines for implementation, refactoring, and review.
Git Worktree Setup
k8zdev/k8z
Automate git worktree creation and copy private files (not tracked in git) to new workdirs.
Bump Version
VeryGoodOpenSource/very_good_analysis
Bumps the verygoodanalysis package to a new version. An agent skill from VeryGoodOpenSource/very_good_analysis.
More from flutter/devtools
All 10 skills in this repoAdding Release Notes
flutter/devtools
Adds user-facing change descriptions to DevTools release notes.
Adding 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.
Related
Works with
Categories
Questions about Updating Package Versions
What does Updating Package Versions do?
Guides updating dependency versions in published packages to avoid mono-repo resolution failures. Updating Package Versions is an agent skill from flutter/devtools. Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
When should I use Updating Package Versions?
Updating Package Versions fits situations like: development work in your project.
How do I install Updating Package Versions in Claude Code?
Run `npx skills add flutter/devtools --skill updating-package-versions -a claude-code`. Or copy the skill folder (.agents/skills/updating-package-versions in flutter/devtools) into .claude/skills/updating-package-versions in your project. Claude Code loads it when a task matches its description.
How do I install Updating Package Versions in Codex?
Run `npx skills add flutter/devtools --skill updating-package-versions -a codex`. Or copy the skill folder (.agents/skills/updating-package-versions in flutter/devtools) into .agents/skills/updating-package-versions in your project. Codex loads it when a task matches its description.
Can I use Updating Package Versions 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 updating-package-versions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/updating-package-versions, .gemini/skills/updating-package-versions, .github/skills/updating-package-versions and .opencode/skills/updating-package-versions in your project.
What does Updating Package Versions need to run?
Going by SKILL.md and its folder, Updating Package Versions needs the command-line tools its instructions call (flutter).
Does Updating Package Versions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Updating Package Versions 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. Review the folder before installing.
What licence does Updating Package Versions use?
Updating Package Versions 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 Updating Package Versions use?
About 556 tokens (SKILL.md is roughly 2.2k 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 Updating Package Versions?
Skills that share tags, products or a category with Updating Package Versions: Code Review (flutter/flutter, 179k stars), Senior Architect Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars) and Code Guidelines (getsentry/sentry-dart, 873 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Updating Package Versions?
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.