/update-flutter-deps
Safely update Flutter dependencies. Trigger with "update Flutter packages", "update pubspec.yaml", "upgrade Flutter deps".
$ npx -y skills add wasabeef/claude-code-cookbook --skill update-flutter-deps --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/update-flutter-deps
Context preview
The summary Claude sees to decide when to auto-load this skill.
Safely update Flutter dependencies. Trigger with "update Flutter packages", "update pubspec.yaml", "upgrade Flutter deps".
SKILL.md
update-flutter-deps.SKILL.mddescription: 'Safely update Flutter dependencies. Trigger with "update Flutter packages", "update pubspec.yaml", "upgrade Flutter deps".'
allowed-tools:
- Bash(flutter *)
- Bash(dart *)
- Read
- Edit
Safely update Flutter dependencies
Safely update dependencies in your Flutter project.
Usage
# Check dependency status and request Claude's help
flutter pub deps --style=compact
"Please update the dependencies in pubspec.yaml to their latest versions"
Basic Examples
# Check current dependencies
cat pubspec.yaml
"Analyze this Flutter project's dependencies and tell me which packages can be updated"
# Check before upgrading
flutter pub upgrade --dry-run
"Check if there are any breaking changes in this planned upgrade"
Integration with Claude
# Comprehensive dependency update
cat pubspec.yaml
"Analyze Flutter dependencies and perform the following:
1. Research the latest version of each package
2. Check for breaking changes
3. Evaluate risk level (safe, caution, dangerous)
4. Suggest necessary code changes
5. Generate updated pubspec.yaml"
# Safe, gradual update
flutter pub outdated
"Update only packages that can be safely updated, avoiding major version upgrades"
# Impact analysis for specific package update
"Tell me the impact and necessary changes when updating provider to the latest version"
Detailed Examples
# Detailed analysis including release notes
cat pubspec.yaml && flutter pub outdated
"Analyze dependencies and provide the following for each package in table format:
1. Current → Latest version
2. Risk evaluation (safe, caution, dangerous)
3. Main changes (from CHANGELOG)
4. Required code fixes"
# Null Safety migration analysis
cat pubspec.yaml
"Identify packages not compatible with Null Safety and create a migration plan"
Risk Criteria
Safe (🟢):
- Patch version upgrade (1.2.3 → 1.2.4)
- Bug fixes only
- Backward compatibility guaranteed
Caution (🟡):
- Minor version upgrade (1.2.3 → 1.3.0)
- New features added
- Deprecation warnings
Dangerous (🔴):
- Major version upgrade (1.2.3 → 2.0.0)
- Breaking changes
- API removals or modifications
Execution of Update
# Create backups
cp pubspec.yaml pubspec.yaml.backup
cp pubspec.lock pubspec.lock.backup
# Execute update
flutter pub upgrade
# Verify after update
flutter analyze
flutter test
flutter pub deps --style=compact
Notes
Always verify functionality after updates. If issues occur, restore with:
cp pubspec.yaml.backup pubspec.yaml
cp pubspec.lock.backup pubspec.lock
flutter pub get
Read more
description: 'Safely update Flutter dependencies. Trigger with "update Flutter packages", "update pubspec.yaml", "upgrade Flutter deps".' allowed-tools: - Bash(flutter *) - Bash(dart *) - Read - Edit
Safely update Flutter dependencies
Safely update dependencies in your Flutter project.
Usage
# Check dependency status and request Claude's help flutter pub deps --style=compact "Please update the dependencies in pubspec.yaml to their latest versions"
Basic Examples
# Check current dependencies cat pubspec.yaml "Analyze this Flutter project's dependencies and tell me which packages can be updated" # Check before upgrading flutter pub upgrade --dry-run "Check if there are any breaking changes in this planned upgrade"
Integration with Claude
# Comprehensive dependency update cat pubspec.yaml "Analyze Flutter dependencies and perform the following: 1. Research the latest version of each package 2. Check for breaking changes 3. Evaluate risk level (safe, caution, dangerous) 4. Suggest necessary code changes 5. Generate updated pubspec.yaml" # Safe, gradual update flutter pub outdated "Update only packages that can be safely updated, avoiding major version upgrades" # Impact analysis for specific package update "Tell me the impact and necessary changes when updating provider to the latest version"
Detailed Examples
# Detailed analysis including release notes cat pubspec.yaml && flutter pub outdated "Analyze dependencies and provide the following for each package in table format: 1. Current → Latest version 2. Risk evaluation (safe, caution, dangerous) 3. Main changes (from CHANGELOG) 4. Required code fixes" # Null Safety migration analysis cat pubspec.yaml "Identify packages not compatible with Null Safety and create a migration plan"
Risk Criteria
Safe (🟢): - Patch version upgrade (1.2.3 → 1.2.4) - Bug fixes only - Backward compatibility guaranteed Caution (🟡): - Minor version upgrade (1.2.3 → 1.3.0) - New features added - Deprecation warnings Dangerous (🔴): - Major version upgrade (1.2.3 → 2.0.0) - Breaking changes - API removals or modifications
Execution of Update
# Create backups cp pubspec.yaml pubspec.yaml.backup cp pubspec.lock pubspec.lock.backup # Execute update flutter pub upgrade # Verify after update flutter analyze flutter test flutter pub deps --style=compact
Notes
Always verify functionality after updates. If issues occur, restore with:
cp pubspec.yaml.backup pubspec.yaml cp pubspec.lock.backup pubspec.lock flutter pub get
A collection of commands, roles, and automation scripts for Claude Code. Automate your workflow without unnecessary confirmations, allowing you to focus on what matters.
Repo: wasabeef/claude-code-cookbook
Other skills on claude-code-cookbook.
- /analyze-dependencies
Analyze project dependencies and evaluate architectural health. Trigger with "analyze dependencies", "detect circular dependencies", "architecture issues?", "check module coupling", "find layer violations". Generates dependency matrix, fan-in/fan-out analysis, and prioritized
Open skill - /analyze-performance
Performance analysis based on Core Web Vitals with UX scoring. Trigger with "analyze performance", "improve speed", "check Core Web Vitals", "page speed", "improve LCP", "identify performance issues".
Open skill - /check-fact
Verify information accuracy against codebase and documentation. Trigger with "is this correct?", "fact check", "verify this", "is this accurate?".
Open skill - /check-prompt
Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".
Open skill - /commit-message
Generate commit messages from staged changes. Trigger with "suggest commit message", "generate commit message", "what should the commit say?", "write commit message".
Open skill - /context7
Search technical documentation via Context7 MCP. Trigger with "check the docs", "look up documentation", "how to use this library?", "API reference".
Open skill

