Automated summary
Updates the packages declared in a Flutter project's pubspec.yaml, reviewing changelogs before any change and asking for confirmation on major version bumps.
Strengths
- Fetches the pub.dev changelog (and GitHub release notes when needed) and summarises new features, fixes and breaking changes before upgrading
- Pauses and requests explicit approval through AskUserQuestion whenever a major version change is involved
- Handles a single package, several packages, or the whole project via --all
- Ends with a before/after version table with change type, and suggests re-running build_runner when generated files are present
Limitations
- Relies entirely on flutter pub outdated and flutter pub upgrade: no rollback or automatic pinning if something breaks
- Runs no tests or static analysis to spot API breakage in the project's own code
- Breaking-change detection depends on how complete the upstream changelogs and fetched pages are
Use it when you want to bump Dart/Flutter dependencies in a disciplined way, with a review of what changed before applying it.
Avoid it when you need to untangle complex version conflicts or hand-migrate code broken by a major upgrade.
Security analysis
CautionThe skill performs legitimate Flutter package management tasks using bash and network access. Commands are non-destructive and standard for the domain, but they do modify project files and fetch external content, warranting caution rather than a completely risk-free rating.
- •Instructs execution of bash commands (flutter pub outdated, flutter pub upgrade, build_runner) that modify project dependency state and generate files.
- •Uses WebFetch to access external sites (pub.dev, GitHub) for changelog information.
Examples
/flutter-pub-update --all/flutter-pub-update http dio shared_preferencesUpdate the intl package in my Flutter project; check the changelog and warn me about breaking changes before bumping the major version.name: flutter-pub-update description: Flutterプロジェクトのpubspec.yamlパッケージを更新するスキル。一括更新または指定パッケージ更新に対応。メジャーバージョン更新時は確認を挟み、更新前にpub.dev/GitHubでchangelogを確認して変更内容を報告する。$ARGUMENTSにパッケージ名を指定するか、--allで全パッケージ更新。
Flutter Pub Update
Overview
Flutterプロジェクトのpubspec.yaml依存パッケージを安全に更新するためのスキル。更新前に変更内容を確認し、メジャーバージョン変更時はユーザー確認を挟む。
使用方法
/flutter-pub-update パッケージ名- 指定パッケージを更新/flutter-pub-update パッケージ1 パッケージ2- 複数パッケージを更新/flutter-pub-update --all- 全パッケージを一括更新
ワークフロー
Step 1: 現在の状態を確認
flutter pub outdated
出力から以下を把握:
- Current: 現在のバージョン
- Upgradable: pubspec.yaml制約内で更新可能なバージョン
- Resolvable: 制約を変更すれば更新可能なバージョン
- Latest: 最新バージョン
Step 2: 更新対象の特定
指定パッケージの場合: $ARGUMENTSで指定されたパッケージのみ対象
--allの場合: outdatedで表示された全パッケージを対象
Step 3: 各パッケージの更新差分を調査
対象パッケージごとにWebFetchツールを使用して変更内容を確認:
-
pub.devのChangelogを確認
- URL:
https://pub.dev/packages/{パッケージ名}/changelog - 現在バージョンから更新後バージョンまでの変更点を抽出
- URL:
-
GitHubリリースノートを確認（必要に応じて）
- pub.devのパッケージページからリポジトリURLを取得
- リリースノートで詳細な変更内容を確認
-
変更内容をまとめて報告
- 新機能
- バグ修正
- Breaking Changes（重要）
- 非推奨になった機能
Step 4: メジャーバージョン更新の確認
メジャーバージョンが変わる場合（例: 1.x.x → 2.x.x）:
- Breaking Changesを明確に提示
- 影響を受ける可能性のあるコードを説明
- AskUserQuestionツールで更新の承認を確認
このパッケージはメジャーバージョンが変わります:
- {パッケージ名}: {現在バージョン} → {新バージョン}
Breaking Changes:
- [変更内容1]
- [変更内容2]
更新を続行しますか？
Step 5: パッケージの更新
承認後、flutter pub upgradeコマンドを使用:
指定パッケージの更新:
flutter pub upgrade パッケージ名
メジャーバージョンを含む更新:
flutter pub upgrade --major-versions パッケージ名
全パッケージの更新:
flutter pub upgrade
全パッケージのメジャーバージョン更新:
flutter pub upgrade --major-versions
Step 6: 更新結果の報告
更新完了後、以下を報告:
## 更新完了
| パッケージ | 旧バージョン | 新バージョン | 変更種別 |
|-----------|-------------|-------------|---------|
| xxx | 1.0.0 | 1.2.0 | Minor |
| yyy | 2.0.0 | 3.0.0 | Major |
### 主な変更点
- xxx: 新機能Aが追加
- yyy: APIが変更（要確認）
注意事項
- 自動生成ファイル（*.g.dart, *.freezed.dart）がある場合は
flutter pub run build_runner build --delete-conflicting-outputsの実行を提案
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/flutter-pub-dependency-update-mtzb82tn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/flutter-pub-dependency-update-mtzb82tn/download' --output '.skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md.part' && mv '.skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md.part' '.skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md' && test -s '.skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/flutter-pub-update' && cp -R '.skill-downloads/flutter-pub-dependency-update-mtzb82tn' '.claude/skills/flutter-pub-update'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/flutter-pub-dependency-update-mtzb82tn'openskills read 'flutter-pub-dependency-update-mtzb82tn'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/flutter-pub-dependency-update-mtzb82tn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.