analyze-dependencies
Analyzes your project's dependencies and checks architecture health.
Safely update dependencies in your Rust project.
> /plugin marketplace add wasabeef/claude-code-cookbookHow it fires
How this command gets triggered: by you, by Claude, or both.
/update-rust-depsContext preview
What this command does when you run it.
Safely update dependencies in your Rust project.
Safely update dependencies in your Rust project.
# Check dependency status and request Claude's help cargo tree "Please update the dependencies in Cargo.toml to their latest versions"
# Check current dependencies cat Cargo.toml "Analyze this Rust project's dependencies and tell me which crates can be updated" # Check list of updatable crates cargo update --dry-run "Analyze the risk level of updating these crates"
# Comprehensive dependency update cat Cargo.toml "Analyze Rust dependencies and perform the following: 1. Research the latest version of each crate 2. Check for breaking changes 3. Evaluate risk level (safe, caution, dangerous) 4. Suggest necessary code changes 5. Generate updated Cargo.toml" # Safe, gradual update cargo tree "Update only crates that can be safely updated, avoiding major version upgrades" # Impact analysis for specific crate update "Tell me the impact and necessary changes when updating tokio to the latest version"
# Detailed analysis including release notes cat Cargo.toml && cargo tree "Analyze dependencies and provide the following for each crate in table format: 1. Current → Latest version 2. Risk evaluation (safe, caution, dangerous) 3. Main changes (from CHANGELOG) 4. Trait bound changes 5. Required code fixes" # Async runtime migration analysis cat Cargo.toml src/main.rs "Present all necessary changes for migrating from async-std to tokio or upgrading tokio to a new major version"
Safe (🟢): - Patch version upgrade (0.1.2 → 0.1.3) - Bug fixes only - Backward compatibility guaranteed Caution (🟡): - Minor version upgrade (0.1.0 → 0.2.0) - New features added - Deprecation warnings Dangerous (🔴): - Major version upgrade (0.x.y → 1.0.0, 1.x.y → 2.0.0) - Breaking changes - API removals or modifications - Trait bound changes
# Create backups cp Cargo.toml Cargo.toml.backup cp Cargo.lock Cargo.lock.backup # Execute update cargo update # Verify after update cargo check cargo test cargo clippy
Always verify functionality after updates. If issues occur, restore with:
cp Cargo.toml.backup Cargo.toml cp Cargo.lock.backup Cargo.lock cargo build
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
Analyzes your project's dependencies and checks architecture health.
Analyzes application performance from a user experience perspective and quantifies experience improvements from optimizations. Calculates UX scores based on…
Verifies if a statement is true by checking your project's code and documentation.
A comprehensive collection of best practices for evaluating and improving the quality of prompts for AI Agents. It systematizes knowledge gained from actual…
Generates commit messages from staged changes (git diff --staged). This command only creates messages and copies them to your clipboard—it doesn't run any git…